A branch has been started on this:
https://bitbucket.org/fenics-project/dolfin/branch/garth/use-mpi-communicator
It will hopefully be ready to merge shortly after the 1.3 release.
Garth
On 2013-12-06 13:54, Jan Blechta wrote:
I'd like to introduce support for communicator being supplied by user,
stored within mesh and used by other objects based on the mesh. There
are few applications of this. Mikael has one being rather non-trivial,
I
think.
To achieve this it will require some changes in the interface, roughly
sketched:
- MPICommunicator::MPICommunicator()
+ MPICommunicator::MPICommunicator(const MPI_Comm&
comm=MPI_COMM_WORLD)
+ MPICommunicator::MPICommunicator(const MPICommunicator& comm)
merging classes MPI, MPINonbocking into MPICommunicator
+ Mesh::Mesh(..., shared_ptr<MPICommunicator> comm=MPICommunicator())
+ UnitIntervalMesh(..., comm), ...
Importat question is which type of comm to reaveal to user in C++
DOLFIN, pyDOLFIN to make it as much as possibly compatible with
other libraries, like boost, PETSc, mpi4py, petsc4py.
Jan
_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics
_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics
