> Yeah we use ExodusII most of the time because we can visualize it. Putting
> all of the rest of the meta-data in that format does sound like a good idea
> moving forward, but that's not what we have today. Our users make use of XDA
> when they want to do restart. That's really what we are aiming for here.
> Either way, am I on base here with this proposal?
I don't think you are off base, but I'll review the background & code more
thoroughly. Certainly in the short term our XD{A,R} implementation should
handle all our functionality, but long term I really like the idea of
leveraging a more standard format, if possible.
I'll start looking in to how we might be able to get a refinement hierarchy
into ExodusII, or maybe augment a "flat" exodus mesh with the refinement tree
information required to "unflatten" it, but in the near term adding XD{A,R}
support for your features is certainly the right thing to do.
-Ben
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
