State files failing with changing max time
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
I have numerous users that are having issues with state files pointing to datasets that have a variable number of timesteps. This happens for at least two reasons. One is you create a state fine from one dataset (such as climate for February), and want to then use the same state file on a dataset that is exactly the same, but from another month (March) (28 vs 31 days). The second is if you need to visualize a dataset that is being written, and will be for many days or a few weeks. You want to know it is running correctly. If it is a complex visualization, you want to set up your pipeline once, save a state file, and continuously re-use it on the dataset as it is being written. A common example is simulating a house fire - there are lots of steps to get to a car on fire.
Here is how to replicate this bug. I am providing three datasets, 1 timestep (toy_problem_timestep1.e), 5 timesteps (toy_problem_timestep4.e) and 9 timesteps (toy_problem_timestep8.e).
- Local server, Linux, 4.3.1.
- Open toy_problem_timestep1.e.
- Information tab. Notice that there are no timestep.
- File/ Save State. I am saving as toyC.pvsm
- Edit/ Reset Session.
- File/ Load State. Now, point at toy_problem_timestep8.e. OK.
- Information tab. Notice that there are 9 timesteps. <<bug - notice that the Time toolbar does not have the correct maximum number of timesteps.>>
- Play. Notice that you do see all 9 (0-8)timesteps, and we go to time 2. this is correct. However, I think this is a hidden artifact of my toy dataset - it only goes to 2 seconds. If it went higher, you would also see bugs. We will replicate this next.
- File/ Reset session.
- Edit the toyC.pvsm file.
- <> To make life easier, change all references to toy_problem_timestep1.e to toy_problem_timestep8.e.
- Change line 19, under the Properties name="EndTime", to value="0".
- Save toyC.pvsm.
- In ParaView, open state file toyC.pvsm.
- <> Play. We don't move forward in time. If you look in the Information tab, you can see that the Exodus reader knows about the timesteps, but ParaView doesn't.
- File/ Reset session.
- Edit the toyC.pvsm file.
- Change line 19, under the Properties name="EndTime", to value="1.1" (my user's EndTime is actually around 0.6, so floating point is saved some times.
- Save toyC.pvsm.
- In ParaView, open state file toyC.pvsm.
- <> Play. We don't move forward in time.
- More detail - Open the View/ Animation View. Snap to Timesteps. You only see three timesteps (out of 9).
Solution:
- File/ Reset session.
- Edit the toyC.pvsm file.
- Delete lines 18, 19 and 20 (i.e., name="EndTime").
- Save toyC.pvsm.
- In ParaView, open state file toyC.pvsm.
- <> Play. This will work properly. (However, you never do get the correct max number of steps in the time toolbar.
Sorry for being so verbose, but wanted to be clear.
I will give the datasets to Utkarsh (including the final toyC.pvsm). It is DoNotRelease-reloadStateFileError.tar.gz.