You may be interested in the "Checkpoint" mesh format:
https://github.com/libMesh/libmesh/blob/master/include/mesh/checkpoint_io.h
It is still XDR based... but basically just writes out the raw mesh as it
sits on each processor and then reads it back in during a restart. Because
of this you have
I didn’t know the numbering could change. Now it makes sense. Thanks.
Sincerely,
Miguel A. Salazar de Troya
Graduate Scholar, Lawrence Livermore National Laboratory
Ph.D. Candidate, University of Illinois at Urbana-Champaign
T1878
Rm: 112
Ext: 2-6411
L-code: 288
On 1/14/16, 11:13 AM, "Roy Sto
On Thu, 14 Jan 2016, Salazar De Troya, Miguel wrote:
Sorry the last statement is wrong. Leaving partition_agnostic=true with a
SerialMesh doesn’t return the same assertion error, but the vector written
and the vector read are not the same when I print them. The values seem to
be in different or
Sorry the last statement is wrong. Leaving partition_agnostic=true with a
SerialMesh doesn’t return the same assertion error, but the vector written
and the vector read are not the same when I print them. The values seem to
be in different order.
Miguel A. Salazar de Troya
Graduate Scholar, Lawr
Leaving partition_agnostic=true gives me the same assertion error on
SerialMesh as well.
Sincerely,
Miguel A. Salazar de Troya
Graduate Scholar, Lawrence Livermore National Laboratory
Ph.D. Candidate, University of Illinois at Urbana-Champaign
T1878
Rm: 112
Ext: 2-6411
L-code: 288
On 1/14/16,
In that case, what would be the compatible way to restart the mesh if I
still leave partition_agnostic=false? What would be the way to fix the
code? Leaving partition_agnostic=true doesn¹t avoid the assertion either
for me.
Sincerely,
Miguel A. Salazar de Troya
Graduate Scholar, Lawrence Livermor
