On Thu, May 30, 2013 at 5:09 PM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote:
> > ExodusII is a serial format, and the reader is serial too I think. > ExodusII meshes can be pre-partitioned, however, and the pieces read in > parallel. > > I helped put the capability in a few years ago but don't use it regularly > - perhaps John or some of the MOOSE guys could expand on the preferred way > to preprocess a mesh into pieces? > > A fallback may be to use a single large memory node (if you have one big > enough!) to transform the Exodus file to an XDR file, which could be read > in parallel, but I'd want to check that... > > Following your latter suggestion, I tried using meshtools to convert my .exo mesh to .xdr as meshtool -d 3 -i mesh.exo -p 100 -o htv.xdr It did create a .xdr file, but gave a warning: "Parallel xda/xdr is not yet implemented. Writing a serialized file instead." So, I assume that the -p 100 was inconsequentional for the output. At this stage, should I attempt to read the .xdr file into my code with a ParallelMesh data structure? Would the mesh from this .xdr file be read in parallel, thereby reducing the memory footprint? Thanks, Manav ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
