On Fri, Feb 19, 2016 at 6:56 PM, Roy Stogner <royst...@ices.utexas.edu> wrote:
> > On Fri, 19 Feb 2016, David Knezevic wrote: > > I'm using a SerialMesh, though. Even in the SerialMesh case I would have >> thought the exodus file would depend on the numbering of nodes and elems, >> which is partition dependent, but apparently not? >> > > With SerialMesh we use METIS for partitioning, METIS output is very > number-of-partitions dependent, and our numbering depends on our > partitioning, so it is kind of surprising to get identical Exodus > output on different processor counts. Is it possible that we do a > Hilbert renumbering in Exodus? I thought that was limited to Xdr. > --- > Roy > I looked into this a bit more. There is no Hilbert renumbering as far as I can see. The Exodus data is written out by doing a loop (on processor 0 only) over all nodes and elements, via mesh.nodes_begin()/end() and mesh.active_elements_begin()/end(). The key point, though, is that the order of these loops is is independent of the partitioning, which means that we end up with the same Exodus output with different processor counts. The libMesh solution vector ordering is of course very different with different processor counts, but that doesn't affect the data that gets written out to the Exodus file (the same is true of GMV and presumably the other formats too). David ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
