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.westp...@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, <postgu...@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.westp...@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, <postgu...@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 > > > > > > > > > > > > > > > > > postgu...@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