Hi all,
I've had a bunch of VTU files (say, state1.vtu, state2.vtu,
state2.vtu,...) and using ParaView, it is very easy to display them in
a movie style, being able to "play", "pause", click through the frames
and so on.
I then recently switched to the Exodus format, the information in the
files r
In exodus format, one generally writes all the steps (state1, state2, ...) in
the same file. This relies on the mesh topology being the same for the entire
set of steps.
Greg
On 11/16/10 12:31 PM, "Nico Schlömer" wrote:
Hi all,
I've had a bunch of VTU files (say, state1.vtu, state2.vtu,
sta
> In exodus format, one generally writes all the steps (state1, state2, ...)
> in the same file.
Right; I'll try that later. Moving mesh sequences might also be
represented in one file only I believe.
It's still a bit confusing as to *what ParaView displays when there's
only one state per file.
On 11/16/10 12:46 PM, Nico Schlömer wrote:
In exodus format, one generally writes all the steps (state1, state2, ...)
in the same file.
Right; I'll try that later. Moving mesh sequences might also be
represented in one file only I believe.
It's still a bit confusing as to *what ParaView display
> states in them; as an example, the Sierra codes will output files with names
> similar to "box.e, box.e-s0002, ..., box.e-s0006" In paraview, I can open
> the file "box.e" and it automatically opens all files in the series and
> shows me the combined state times from each file.
Great! This does
Just to complete the thread, a time series of Exodus files is generally called
Exodus restarts. The feature for reading the restarts is documented on the
Wiki:
http://www.paraview.org/Wiki/Restarted_Simulation_Readers#Exodus
Note that the .e-s# naming convention is one way to read them in. An
