time display is wrong for dataset with one timestep
The time display is wrong for datasets that actually do have a time in the dataset, but the dataset only has one timestep. This is impacting a user that has numerous timesteps in a simulation, with one timestep per exodus file. As per my user, the simulation is changing the underlying grid between timesteps, and Exodus can't handle this case in a single file. Thus, one timestep per file.
Attached are three files (files are UUR, as per customer).
- cube_1ts.e: file containing 1 snapshot corresponding to time = 0
- cube_1ts_mod.e: file containing 1 snapshot corresponding to time = 100 -> not displayed properly (paraview thinks time = 0).
- cube_mode.e: file containing multiple snapshots, with the first one corresponding to time = 100 -> this is visualized correctly.
This needs to be fixed.