On Sat, Feb 20, 2016 at 3:53 PM, Derek Gaston <fried...@gmail.com> wrote:
> Yep, you got down to the right thing: with SerialMesh and Exodus we do > partition independent looping on processor 0... so the files always come > out the same. > > However, if you use ParallelMesh with Exodus (yes, that doesn't quite > makes sense to do... but WE do it a lot... especially in our test suite) > beware that the Exodus files will then be partition sensitive (i.e. they > will change order as the number of processors change). I believe this has > to do with the way the mesh is serialized with MeshSerializer. > > Like I mentioned, we do this a lot in our test suite so that we can test > ParallelMesh but still output an Exodus file to compare to the "gold" > standard Exodus file. Because of the reordering we have to use a special > option to Exodiff (which is an Exodus utility that diff's two Exodus > files). That option is "-m" for "map"... what it does is builds a > geometric map between all of the elements/nodes in both files to use for > comparison instead of doing a straight comparison using elements/nodes with > the same IDs. > > I know that's a little off-topic, but I thought I would leave it here in > case anyone else is trying to do something similar. > > Derek > Great info, thanks!! 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
