Hi John,
The following codes are used for import and export mesh and solution.
//============= import mesh ===============
DistributedMesh mesh(init.comm());
mesh.read("BOX.cpr");
//=======================================
//============ export solution ==============
MeshSerializer serialize(mesh);
Nemesis_IO(mesh).write_equation_systems (file_name.str(),equation_systems);
//=======================================
In fact, I was trying to avoid using "MeshSerializer", since it took too much
memory. Did I miss anything to ouptut solution in nemesis format? Should I
write out mesh as well? Could you suggest a successful example to write out
solution and mesh in parallel through each processor?
Thanks a lot
Ken
________________________________
From: John Peterson <[email protected]>
Sent: Monday, January 28, 2019 6:16 AM
To: Bin Liu
Cc: [email protected]
Subject: Re: [Libmesh-users] output results of very huge mesh
On Sat, Jan 26, 2019 at 8:47 PM Bin Liu
<[email protected]<mailto:[email protected]>> wrote:
Hi John,
Indeed, I tried NemesisIO. It writes solution into multiple files in parallel.
However, when I tried to open these files with paraview, the paraview reported
an error, saying "Cannot find any mesh". What's could be my mistake here?
Well, the API is admittedly a bit difficult to use correctly, so it's possible
you need to call it differently. It's also possible there is a bug... if you
could post the code you used to write the Mesh and let us know what version of
libMesh you are using, that might help us track down the issue.
--
John
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
