Need ability to read single restart files in ExodusII
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
e-mail thread. Basically, they want the ability to open individual files of the type file.e-s002.
David,
I think it is working correctly with a full sequence of files (e.g. e, e-s001, e-s003, etc). The issue is what if you only want to load one restart file (e.g. only load file.e-s003)? The reader assumes there is a series and tries to find the .e-s001 file and bombs -- at least you get an unable to open file.e-s002 for reading error. You have to rename the file to .e in order to open a single restart file.
John
It is the standard format for Sieere restart files. They are partitioned by time with possibly overlapping time steps. It is in fact possible to have files of the form name.e.16.00-s0002 as well where there are 16 geometric partition for each of the restarts. We had a feature request for automatically handling this format at one time, and I think we got it working for a few versions, but lost the capability in the last exodus reader rewrite.
Hmmm... I haven't fiddled with the Exodus reader in a while and I see that Ken checked in ParaView/Servers/Filters/vtkExodusFileSeriesReader.h in May'08 specifically to handle restart files. Do you know when the behavior changed? What version of ParaView have you tried? It looks like the file-series-reader has the PV 3.4.0 tag but I haven't checked to make sure that it's actually used by the GUI.
David
Dave T, I am getting a request from a user that ParaView be able to open files named file.e-s0003. Do you think this would be a good idea, and how should we go about getting it implemented? Want me to write up a bug and assign it to you?
Alan
Alan,
Thanks for looking into this. Unfortunately, this is the file naming convention for all Sierra codes that write exodus files. They are written as
file.e, file.e-s0002, file.e-s0003, etc.
This convention is understood by Ensight. For example if I request to open all files
file.e*
all of the files above would be read in. I can also open any of these files individually in Ensight. The same behavior in ParaView would be desirable.
Thanks, Brian
I have an ExodusII file that gets named
tank_discreteAdjoint_2d_out_recovery.e-s0002
When I try to load in paraview (3.2.1) as an ExodusII file I get errors. Brian Wylie suggested that paraview is probably thinking that this is a sequence of files, when in fact it is only a single file.
The file is loaded correctly when I rename it as
tank_discreteAdjoint_2d_out_recovery.e
If you need more information, please contact me. I am running paraview on the SCICO LAN.
Thanks, Brian