On 3/15/10 12:34 PM, David Knezevic wrote: > Cody Permann wrote: > The other real issue here though is that the exodus format does not > support a changing mesh in the same file (to the best of my knowledge). > One must write a new mesh file each time the mesh changes and deal with > that on the visualization side. > > Well we had write a new file for each time step with gmv anyway, so > exodus is no worse off on that front (and it's better off for static > mesh problems)
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. -- Boyce ------------------------------------------------------------------------------ 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
