I’m starting a python trace, after which I’m choosing to load a ParaView .pvsm state. In the load state window, I’m changing the filename to select a different data file. Then on stopping the trace, I see that the LoadState function has popped up in trace, but it lacks the argument that a file different from the saved state was selected. How to get around this, and have a python code with a different file passed in LoadState generated by trace. This is useful as I want to use this trace with the file later provided as a command line argument by modifying the python trace code.
Looks like an issue to me, please open it: https://gitlab.kitware.com/paraview/paraview/-/issues
I have been dealing with the same problem. Is there any solution yet for this?
Of course not, the issue has just been created.
Fair enough,
For those dealing with a similar issue I found a simple workaround by just skipping the load state, and programming the trace script to perform the steps needed to get to where the load state would’ve taken me otherwise. In my case my load state had something like 8 clips and 2 calculators, so I just made the trace script to manually perform the 8 clips and 2 calculators.
It’s annoying, especially if the load state loads a huge amount of functions. But once you write it once you can copy and paste the script to have it work for all filenames you need to get data from.
Hopefully that can help others stuck in the same position!
I have been personally doing this. But it is a pain if the workflow is too long or if you do any mistake along the way, all of that also gets recorded which can add a lot of unnecessary compute times while getting applied on large datasets.