On Thu, 7 Feb 2013, Derek Gaston wrote:
I thought it would be as easy as swapping out libMesh::COMM_WORLD
(and setting libMesh::libMeshPrivateData::_n_processors and
_processor_id)... but there is this Parallel::Communicator CommWorld
thing that doesn't use libMesh::COMM_WORLD that is kind of standing
in the way.
Right - that's what everything actually uses.
But there's nothing stopping you from swapping that out too. Go ahead
and add a Communicator::swap() method.
I mean, we could go do a huge redesign of libMesh so that every
object takes a COMM in its constructor (or references one from an
associated object like an EquationSystems object or something).
That's effectively going to be the final design, I'm afraid - either a
new optional constructor argument or a new Communicator getter/setter
method for most of the big parallel objects.
I hadn't planned on actually taking that step any time soon, but I
could push it up the TODO list if you'd find it useful.
---
Roy
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
