Exodus reader fails for bad time_whole steps
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The Exodus reader fails reading in time data if the 'time_whole' entry is bad. EnSight does read these files correctly, in the sense that you can actually see the time steps (even if they have incorrect times.). This is confusing and needs to be fixed.
Attaching a file that shows the problem. Open the dataset, and you will see that it looks like there is only one timestep in the dataset.
Linux, 4.4.0, local server. There are 100 timesteps in this dataset.