On Nov 6, 2013, at 8:54 PM, Cody Permann <codyperm...@gmail.com> wrote:
> Let us know where we can help. I was going to element IDs back to the > connectivity arrays in XDA output and also add node IDs to that format for > the first time too. That might be counter-productive if you are going > another direction. > Sure - I'll make a branch to implement the parallel mesh XDA output. I expect in the parallel files we'll need element ID and node ID. It took a lot of work in the serialized implementation to get those inferred by position, and I don't see any reason to mess with that. I actually expect the parallel mesh XDA bit to be pretty straightforward. As for alternatives, I've looked into HDF5 and the like, and I am not at all sold… I'm open for discussion, though. -Ben ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
