ExodusII: Time steps wrongly ordered
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
Exodus files that contain several states associated with time steps typically store those in ascending order in the file. It may happen though that "time" really represents another scalar parameter quantity which is allowed to decrease from one step to another. The file found at http://win.ua.ac.be/~nschloe/other/solution.e is an example.
What ParaView does for those files is reorder the states found in the file by time instead of taking the order in which they are stored. This leads to unwanted behavior with observing the data.
VTK has the ability of reading individual, int-indexed time steps, cf. http://www.vtk.org/doc/nightly/html/classvtkExodusIIReader.html#a37e8d6c7118877de07fa140b5d5eb8c3. The suggestion would be to remove the code that explicitly orders the time steps by their time value, and display the states in the natural int-indexed order that is stored in the file.