[Paraview] [EXTERNAL] Re: Lock Data Range for multiple attributes

Fri Oct 7 13:07:21 EDT 2016

This was implemented within the last few months, closed and tested.  This functionality will appear in the 5.2.0 release, which is scheduled for Super Computing next month.

https://gitlab.kitware.com/paraview/paraview/issues/16052

Alan

On 10/7/16, 7:32 AM, "ParaView on behalf of Paluszek, Lukasz" <paraview-bounces at paraview.org on behalf of lukasz.paluszek at airbus.com> wrote:

>This was already reported as a bug (see the attached email). Perhaps this is a good opportunity for a little reminder ;-)
>
>Regards,
>Lukasz
>
>
>Łukasz Paluszek
>Airbus Helicopters
>Aerodynamics Department (ETGAI)
>86607 Donauwörth
>Germany
>Tel.: +49 (90) 671 8231
>Fax.: +49 (90) 671 9122
>Lukasz.Paluszek at airbus.com
>
>-----Original Message-----
>From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of postgurke at web.de
>Sent: 15 September 2016 12:41
>To: Mathieu Westphal
>Cc: paraview
>Subject: Re: [Paraview] Lock Data Range for multiple attributes
>
>Mathieu
>
>Thank you so much!
>It seems that I can have other color values in between the min/max (so I don't have to remove all the dots), but the scale must contain the min/max contained in the attribute data as limits. I now understand what you meant in your previous e-mail...
>Yes, the color bar is not optimal, but right now I care more for a consistent coloring of all objects.
>
>Maybe the Lock Data Range function could be made to work in this scenario as well in a future PV version. That would still be very helpful :).
>
>Thanks again
>Venke
>
>
>
>
>
>> Mathieu Westphal <mathieu.westphal at kitware.com> hat am 15. September
>> 2016 um
>> 12:03 geschrieben:
>>
>>
>> Hello Venke,
>>
>> Sure, here is the process to set up the lookuptable correctly with the gui:
>>  - Open ParaView
>>  - Open your data
>>  - Color with the data you want to "lock"
>>  - Show the Color Map Editor ( Right Click on toolbar, Color Map
>> Editor)
>> - Click on the cogwheel to show advanced options
>> - Click on the dot on the color line (below the graph) to remove all
>> data point except the minimum and maximum
>> - Click on the color line (below the graph) to add two datapoint
>> approximativally around the locked range you want to set
>> - Set the correct value for the data point you just added in the table
>> - Copy the RGB color of the minimum and maximum into your locked range
>>
>> Done
>>
>> A side effect is the scalar bar does not show the information you
>> want, but the color on the mesh are correct.
>> In Any case, the "Lock Data Range" option should work, but it doesn't,
>> so it looks like a bug to me.
>>
>>
>> Regards,
>>
>>
>> Mathieu Westphal
>>
>> On Thu, Sep 15, 2016 at 11:30 AM, <postgurke at web.de> wrote:
>>
>> > Hello Mathieu
>> >
>> > Thank you for your answer. Unfortunately I don't quite understand
>> > :(. I tried to duplicate the first and last point of LUT.RGBPoints
>> > (which are initially correct before I look at a different attribute
>> > and switch back) - but this does not do the trick. Sorry, I am not
>> > used to reading from State-Files. Do you have a short explanation
>> > what you did in either the Paraview python shell or GUI to achieve
>> > this?
>> >
>> > Cheers
>> > Venke
>> >
>> >
>> >
>> > > Mathieu Westphal <mathieu.westphal at kitware.com> hat am 15.
>> > > September
>> > 2016 um
>> > > 10:46 geschrieben:
>> > >
>> > >
>> > > Hello
>> > >
>> > > There is an easy work around for this. Do not use the lock range
>> > > feature, but add lookup table point on the data value you want to lock.
>> > > See attached pvsm, locked data are RTData and Results.
>> > >
>> > >
>> > >
>> > >
>> > > Mathieu Westphal
>> > >
>> > > On Thu, Sep 15, 2016 at 9:44 AM, <postgurke at web.de> wrote:
>> > >
>> > > > Hello
>> > > >
>> > > > Does nobody have a solution for this, or am I missing something
>> > obvious?
>> > > > The only thing I can do to fix the color ranges is separate the
>> > > > file
>> > into
>> > > > multiple objects, but as one can only look at one at a time
>> > > > anyways (as they are at the same location, obviously) and our
>> > > > model already contains a lot
>> > of
>> > > > objects, this is rather bothersome...
>> > > >
>> > > > Cheers
>> > > > Venke
>> > > >
>> > > >
>> > > >
>> > > > > postgurke at web.de hat am 9. September 2016 um 09:52 geschrieben:
>> > > > >
>> > > > >
>> > > > > Hello All
>> > > > >
>> > > > > Sorry to bother you again... I seem to miss something wanting
>> > > > > to fix
>> > > > color
>> > > > > scale
>> > > > > ranges for objects with multiple attributes.
>> > > > > For example: I have a vtk-Plane with associated velocity and
>> > > > > density
>> > > > values
>> > > > > that
>> > > > > I can choose for coloring. When I imported the object, I set
>> > > > > LUT.RescaleTransferFunction(min, max) and LUT.LockDataRange =
>> > > > > 1 for
>> > both
>> > > > > attributes (with different min,max, of course). In the GUI
>> > > > > everything
>> > > > looks
>> > > > > fine
>> > > > > at first, but when I switch the coloring from one attribute to
>> > another,
>> > > > > ParaView
>> > > > > seems to ignore the checked "Lock Data Range" but switches to
>> > > > > some
>> > > > Min/Max
>> > > > > found
>> > > > > in the data. Maybe I misunderstand the functionality of "Lock
>> > > > > Data
>> > > > Range"? Is
>> > > > > this the expected behaviour? If yes, what could I do to really
>> > > > > fix
>> > the
>> > > > min,max
>> > > > > to my own specification? (I also tried to use a preset color
>> > > > > scale
>> > with
>> > > > my
>> > > > > desired min,max, but this does not change the behaviour
>> > > > > either.)
>> > > > >
>> > > > > Thanks for your support and any ideas on this, Venke
>> > > > > _______________________________________________
>> > > > > Powered by www.kitware.com
>> > > > >
>> > > > > Visit other Kitware open-source projects at
>> > > > > http://www.kitware.com/opensource/opensource.html
>> > > > >
>> > > > > Please keep messages on-topic and check the ParaView Wiki at:
>> > > > > http://paraview.org/Wiki/ParaView
>> > > > >
>> > > > > Search the list archives at:
>> > > > > http://markmail.org/search/?q=ParaView
>> > > > >
>> > > > > Follow this link to subscribe/unsubscribe:
>> > > > > http://public.kitware.com/mailman/listinfo/paraview
>> > > > _______________________________________________
>> > > > Powered by www.kitware.com
>> > > >
>> > > > Visit other Kitware open-source projects at
>> > > > http://www.kitware.com/ opensource/opensource.html
>> > > >
>> > > > Please keep messages on-topic and check the ParaView Wiki at:
>> > > > http://paraview.org/Wiki/ParaView
>> > > >
>> > > > Search the list archives at:
>> > > > http://markmail.org/search/?q=ParaView
>> > > >
>> > > > Follow this link to subscribe/unsubscribe:
>> > > > http://public.kitware.com/mailman/listinfo/paraview
>> > > >
>> >
>_______________________________________________
>Powered by www.kitware.com
>
>Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
>Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
>Search the list archives at: http://markmail.org/search/?q=ParaView
>
>Follow this link to subscribe/unsubscribe:
>http://public.kitware.com/mailman/listinfo/paraview
>
>This mail has originated outside your organization, either from an external partner or the Global Internet.
>Keep this in mind if you answer this message.
>
>
>AIRBUS HELICOPTERS DEUTSCHLAND GmbH
>
>Sitz der Gesellschaft / Registered Office: Donauwörth
>
>Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508
>
>Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury
>
>Geschäftsführung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Schübel; Stefan Thomé
>
>The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
>If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
>Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
>All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
>