On Wed, 27 Aug 2014, Miguel Angel Salazar de Troya wrote:
Thanks. ParallelMesh::allgather() is going to be pretty useful for
me. Yes, my part of the code that would run in the entire mesh would
be pretty small. Could I rebuild the ParallelMesh in each processor
once I'm done?
Not so much "rebuild" as "unbuild".
ParallelMesh::delete_remote_elements() will remove all the
non-semilocal elements, cutting your memory use to O(n_elem/n_proc)
instead of O(n_elem) again.
Also, one question related with MPI and clusters. I have little
experience on clusters, only some homework on MPI. I've thought of
compiling my program with static libraries and avoid the hassle of
installing the libraries on the cluster. Is this a recommended
option? Is this possible with libmesh?
I wouldn't say it's recommended, but it should definitely be possible.
I generally do personal builds of whatever I don't trust the
cluster/supercomputer sysadmins to do correctly, but those are still
shared library builds. I'd recommend the same to you, except: we're
getting ready to release libMesh 1.0 and I'll bet nobody has tested a
"--enable-static --disable-shared" build recently. If you're
considering doing so I'd appreciate hearing whether it worked or
whether you encountered problems.
Thanks,
---
Roy
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
