Does anyone know if the save/load state works fine when the state pipeline includes a Transform filter? I consistently received errors while loading a state that incudes the Transform filter. When I did not include the Transform filter in the pipeline, I can load the state just fine. Here’s a little info:
-I made sure that the data file is in the same directory as the state file
-Here is some snapshots of the error message:
Anyone finds any workaround on this?
Does anyone know if the save/load state works fine when the state pipeline includes a Transform filter?
Please share steps to reproduce the problem
-Load VTS file (3D structured mesh)
-Apply Transform filter (assign Z-scale multiplier only of 1000)
-Apply Calculator filter
-Apply Tube filter
Tube requires a polydata input, which the calculator output is not.
That works, thank you! So, any filter that requires the polydata input should not be included while building the state pipeline? And, is there an easy lookup table that lists all the filters that require the polydata input?
Not true, what is not working is incorrect pipeline setup, with or without state file.
However, the GUI literally prevents you to do use the wrong filter, how are you building your pipeline to work around that ?
And, is there an easy lookup table that lists all the filters that require the polydata input?
Not really no, but once again, the GUI prevents you from doing wrong things.
Below is my pipeline. First, I opened the vts file manually. Then, I ran a macro to generate the remaining portion (like everything up to the “Arrow1”). Does it mean that I cannot include macros to build the state?
Your macros is likely producing the invalide pipeline state. You can use macros, but you need to fix it.
Got it. What would be the advantage of using “load state” than running macros? I wonder if I can discuss this here on the same thread.
Macros and actually very close to python state files, so in a sense, theyr are the same, however macros appears in the macros menus and can be applied generally on a active pipeline, while python state file generally setup a complete pipeline.
.pvsm state file however are XML based, so hard to manually edit and changes, but they are more resilient when sharing with a colleague for example.
more doc here: 8. Saving Results — ParaView Documentation 5.9.1 documentation
Thanks a lot! Problem solved.