On Tue, 28 Nov 2017, Zack Vitoh wrote:
*Question 2*
For the cases above, I noticed that I am no longer running libmesh in
parallel when I read in the mesh. I found, and tried to use
libMesh::Partitioner part();
// Partitioner()::partition_unpartitioned_elements(mesh);
// Partitioner.partition_unpartitioned_elements(mesh);
but I am not sure how exactly this works. Also, I am not sure if using
this the right approach?
Nope. The right approach for most users is to do nothing! In theory,
you just read in your file the same way you would in serial, and if
you're running in parallel then libMesh will automatically partition
the Mesh over the ranks in the communicator you used for it.
*Question 3*
This is less important, as I may have sidestepped this for now, but I'm
sure it will return with a vengeance.
I looked through the forums to find out how VTKIO::write_nodal_data works,
and from there looked into the source for VTKIO::write_equation_system to
see if I could figure out how the former is used in the latter, but to no
avail. I'm writing using exo_io.write_timestep for now, but my screen
(rightly?) reprimands me for doing so.
I have a sense that this will involve a host of other functions
(allgather?) so I may send this as a separate email question.
I don't use VTKIO myself, but IIRC it's supposed to be pretty easy: a
line from our example files like
VTKIO (mesh).write_equation_systems ("out.pvtu", equation_systems);
reads your EquationSystems' data and handles the parallel
synchronization (If necessary? I think pvtu is a parallel output
format...) and so itself.
---
Roy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
