User Issue Needs Replication and Diagnosis: State file shenanigans with volume rendering and sidesets
User Issue. Needs Replication and Diagnosis: State file shenanigans with volume rendering and sidesets.
Is this a dataset issue, or a ParaView-related issue?
ParaView Version: 5.12.0. Remote-server connection.
OS: Client-side: Linux. Server-side: Linux
Decently large dataset; use 16 procs if possible. DO NOT RELEASE DATASET.
To Replicate:
- Start remote-server connection
- Load provided dataset from the remote server (Cory Q should have it). Should be called suo_anttila_*
- Choose a variable to color by. Volume Render the dataset.
- Load the dataset again (there should now be two datasets in the pipeline)
- For this dataset, turn off blocks, turn on any sideset. Color by any variable, if you wish
- Save state. Save as .pvsm and .py
- Reset Session. Still on the Remote Server: Load State. Both state files should crash ParaView.
We found some workarounds for the user, which they should be fine with for now. Hence the lower priority:
- Doing the above process, but purely on the built-in server doesn't crash.
- Doing the above process on the remote-server (up to saving the state file), then loading the state file on the built-in server doesn't crash (assuming the dataset is in the same directory on the client-side as well).
- Do the above process, but wait to enable volume rendering until after you load the state file.
- Do the above process, but in the saved *.py state file, move the line where it sets the representation to volume (suo_anttila_...Display.Representation = 'Volume') to the end of the state file. Loading this modified file doesn't crash ParaView.
Edited by Alex Pelletier