[Paraview] volume color transfer table.
Utkarsh Ayachit
utkarsh.ayachit at kitware.com
Fri Nov 7 12:10:59 EST 2014
Yes, that's a shortcoming of the current implementation. We'll plan to
fix this by 4.4 or sooner.
Utkarsh
On Fri, Nov 7, 2014 at 11:58 AM, Burlen Loring <burlen.loring at gmail.com> wrote:
> that is indeed annoying, and would be very nice to be able to save the
> opacity table. A work around is use a state file. The opacity tables will be
> saved/restored. note: 4.2 has a bug in state file loading re: time.
> depending on your scenario you may need to use 4.1.
>
>
> On 11/07/2014 08:33 AM, Anderson, Lawrence S. wrote:
>>
>> thanks for the attention! I should also point out that i have tried the
>> import/export options on the color table editing feature- opacity is not
>> preserved. i.e. when i export a table to an xml file, the opacities all
>> revert to 1.0, and when i import an xml file, any ' o="x.xx" ' value is
>> ignored, and whatever opacity function in the editor from previous work is
>> applied instead.
>> cheers-
>> -lawrence a.
>>
>> ________________________________________
>> From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com]
>> Sent: Friday, November 07, 2014 9:01 AM
>> To: Anderson, Lawrence S.; Aashish Chaudhary
>> Cc: paraview at paraview.org
>> Subject: Re: [Paraview] volume color transfer table.
>>
>> To the best of my knowledge, the current volume mappers in
>> VTK/ParaView need to use a color/opacity transfer functions. Aashish,
>> is that changing with the new volume rendering code?
>>
>> Utkarsh
>>
>> On Wed, Nov 5, 2014 at 3:12 PM, Anderson, Lawrence S.
>> <LAWRENCE.ANDERSON at utoledo.edu> wrote:
>>>
>>> hi- i have seen this question on various blogs, but not the answer in a
>>> usable form for me...
>>> i provide project data to paraview via vtk legacy files in ascii. the
>>> default color mapping functions provided by paraview do not decouple
>>> opacity
>>> from color, so i am providing my own look_up table of RGBa values
>>> organized
>>> in such a way that i can apply different opacities to the same color, and
>>> different colors to the same opacity. it works for surface rendering,
>>> but
>>> not for volume rendering- i.e. when choosing the volume option, the
>>> rendering reverts back to one of the default tables. how do i apply my
>>> scalar color table in the vtk file to volumes?
>>> i could laboriously enter 120x4 values into the paraview mapping editor,
>>> but
>>> that seems silly...
>>> thank you!
>>> and as i am new to paraview and this list mail option, feel free to refer
>>> me
>>> to an old post.
>>> -lawrence anderson, university of toledo
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>> 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
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>
>
More information about the ParaView
mailing list