On Mon, 15 Mar 2010 20:06:03 -0600, Derek Gaston <[email protected]> wrote: > On Mar 15, 2010, at 11:35 AM, Boyce Griffith <[email protected]> > wrote: > > > FWIW, this is precisely where VisIt has its greatest problems with > > exodus files. > > > > It is my understanding that VisIt expects all of the timesteps for a > > time-dependent simulation to be in the same exodus file. In > > particular, > > if you have multiple single-frame exodus files (e.g., each > > corresponding > > to a different timestep within a time-dependent simulation), VisIt > > cannot treat the collection of files as coming from a single > > time-dependent simulation, making it extremely cumbersome to "play > > back" > > the simulation. > > > > My impression from corresponding a bit with the VisIt developers on > > this > > is that this limitation of the exodus reader per se, but is really a > > more fundamental limitation. > > Well... Next time they tell you that, just tell them that Ensight > handles it beautifully. It really has nothing to do with Exodus.
VisIt's reader plugin design makes a distinction between "multiple time" (a single file may contain multiple steps) and "single time" (each file contains exactly one step) readers. Prior to recent commits (r9703 & r9706), VisIt would not group a series of files with "multiple time" readers. This will be in the 2.0 release whenever that happens (soon, theoretically). So when they said it was deeper than the reader, they meant that it was the fault of VisIt internals, not that the Exodus format was somehow incapable of it. Jed ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
