State files don't read variables from input dataset
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
When you save and then restore a run from a state file, ParaView correctly asks for the directory and name of the dataset. It should then read what it can from the new dataset. Currently, ParaView reads variable data from the state file, and if this is different than the new dataset, ParaView acts poorly.
I have a trivial example using can.ex2 that shows bad behavior.
I made the file can-sparse.ex2 by turning off EQPS and VEL (one point and one cell array). I then saved data as exodus data.
I have also made state files, named can-sparse-state.pvsm, can-state.pvsm and can-state-vel.pvsm that you can use to debug. Instructions below include making these files.
-
Unzip the attached file.
-
ParaView master, Linux (or Windows), local server.
-
Open file can-sparse.ex2. All variables on. Apply.
-
File/ Save State/ can-sparse-debug.pvsm. OK.
-
Disconnect.
-
File/ Load State/ can-sparse-debug.pvsm. Change file to can.ex2. OK. <> - Notice that EQPS and VEL are not available. This is a bug.
-
Open file can.ex2. All variables on. Apply.
-
File/ Save State/ can-debug.pvsm. OK.
-
Change color to VEL.
-
File/ Save State/ can-debug-vel.pvsm. OK.
-
Disconnect.
-
File/ Load State/ can-debug.pvsm. Change file to can-sparse.ex2. OK. <> - Notice that EQPS and VEL show up in the Properties tab, although they are not in the input dataset. This is a bug.
-
Disconnect.
-
File/ Load State/ can-debug-vel.pvsm. Change file to can-sparse.ex2. OK. <> - You get an output note that ParaView could not determine array range. Couldn't we say something that makes more sense? Like "Necessary variable array VEL is missing from input dataset"? This is a bug.
I am marking this high priority, since this is impacting some of our CAM data. If these modifications have to happen in the reader, they need to happen in the CAM reader also.