Global data writer is bad for exodus
I am pretty sure that the Exodus writer is broken for global data, especially for strange timesteps. Here is how to replicate using can.exo.
-
Linux, master, builtin server. ( v5.6.0-1290-gb61f9464 )
-
Load can.exo. All vars on. Apply.
-
Extract Timesteps filter. Select Time Range. Timestep 0 to 19. Apply.
-
File/ Save Data/ save as Exodus. Save as canA. (It will write out a canA.e file). Save all timesteps.
-
CHANGE Extract Timesteps filter. Select Time Range. Timestep 20 to 43. Apply.
-
File/ Save Data/ save as Exodus. Save as canB. (It will write out a canB.e file). Save all timesteps.
-
Edit/ Reset Session.
-
Load canA.e, load all variables, apply.
-
Plot global variable over time. Apply. Turn off everything other than NSTEPS. Notice this is a straight line.
-
Load canB.e, load all variables, apply.
-
Plot global variable over time. Apply. Turn off everything other than NSTEPS. Notice this is a straight line.
-
Change visibility of the canB plot global variables over time to also be in the canA.e plot global variables over time.
This should be a straight line, rather than two slanted, parallel lines.
You can see this occurring if you output canA.e and canB.e into two spreadsheets. canB.e restarts NSTEPS at 0, where in the original data it is fairly large.