← Back to team overview

dolfin team mailing list archive

manager classes

 

We have a problem at the moment when using PETSc related to conflicts between dolfin::MPIManager and dolfin::PETScManger as to who should initialise and finalise MPI. The difficulty is that we can't control the order in which MPIManager and PETScManager are destroyed.

Given that we will probably have more 'manager' classes in the future (e.g. for Trilinos), what is the best approach? Some possibilities are one 'Manager' class that does the lot, or a SingletonManager which can control the order in which singleton manager classes are destroyed. Ideas?

Garth


Follow ups