Sure - I understand. But a specialization for SerialMesh would make a lot of sense in this case - saving a ton of parallel communication (and making it possible to produce the exact same XDA file on one processor or thousands)
Derek Sent from my iPhone > On Nov 6, 2013, at 6:51 PM, "Kirk, Benjamin (JSC-EG311)" > <benjamin.k...@nasa.gov> wrote: > > On Nov 6, 2013, at 5:59 PM, Derek Gaston <fried...@gmail.com> > wrote: > >> Here's another issue: Why are we doing so much parallel communication of >> meshes in the case of Serial mesh? Why doesn't processor zero just go >> through and write the mesh out exactly as it is to XDA? Instead - there is >> a complicated routine that does a lot of parallel communication to push all >> of the pieces through processor 0 from all the other processors…. > > the answer to this one is actually easy: > > e.g. write_serialized_…(), the private implementation, is just a bad naming > convention. What is meant by that is 'write … to a serialized file'. The > implementation works for a serial or parallel mesh, and uses communication to > gather data to write to a serialized file. Rather than maintain two > implementations, we just always proceed as if the source mesh is distributed. > > -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
