Python Trace with all properties stored doesn't properly store custom transfer function information in the trace
I did some testing on when custom transfer functions are contained in the state or trace files and it looks like both the pvsm and Python state files store the custom transfer function properly. The Python trace doesn't store the custom transfer function information in the trace file. I think I set the proper parameters when initiating the Python trace. This was with PV master as of May 4th, 2022. Here's my steps to reproduce:
- Create a custom transfer function in ParaView, preferably one with a unique transparency controls and save that as a custom transfer function.
- Exit ParaView.
- Start ParaView and Start Trace. Then change
any modified properties
toall properties
and check theFully Trace Supplemental Proxies
options for the trace - Create a
Wavelet
source, choose the Volume rendered view and choose the custom transfer function for colormapping - Save a screenshot
- Stop Trace and save as a Python script
- Remove the custom transfer function
- Exit ParaView
- Rename the generated screenshot (to make it easier for comparison)
- Run the generated Python script with
pvpython
It looks like there are numbers for the TF in script but if you look at the images it should be clear that the TF isn't properly getting saved.