On Wed, Aug 12, 2015 at 1:58 PM, Derek Gaston <fried...@gmail.com> wrote:
> Right - that's one of the reasons I created the CheckpointIO Mesh writer: > http://libmesh.github.io/doxygen/classlibMesh_1_1CheckpointIO.html > > Cool, thanks for pointing that out. I remember this being discussed on the list, but I haven't used it before. It only works in the case that you write and read with the same number of processors, right? I'd still like to implement the error checker I mentioned though in order to deal with the N:M case. David > On Wed, Aug 12, 2015 at 1:55 PM David Knezevic <david.kneze...@akselos.com> > wrote: > >> On Wed, Aug 12, 2015 at 1:47 PM, Derek Gaston <fried...@gmail.com> wrote: >> >>> How are you writing out the solution? This certainly doesn't happen >>> when using Exodus (Hilbert keys aren't involved there at all). >>> >> >> It happens if you serialize a system read it back in (e.g. using >> EquationSystems::write/read or >> System::write_serialized_data/read_serialized_data, etc) since that's when >> the Hilbert Keys are used in order to generate a partition-independent >> numbering. >> >> Dave >> >> >> >> ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
