On Tuesday March 22 2011 11:29:23 Garth N. Wells wrote: > Our 'automatic' initialisation of MPI and PETSc is a real mess at the > moment. It seemed to work before by good luck. The major issue is > controlling order in the singleton class SubSystemsManager. For example, > I see that the function SubSystemsManager::init_mpi is called, which set > variables to take responsibility of MPI, and *after* this the > SubSystemsManager constructor is called, which resets that flags. The > end result is that MPI is not finalized. > > I don't see an option other robust option than explicit 'initialise' > (and maybe 'finalise') function calls.
This would then be done by the user in each program? > Any other suggestions? If so it should be possible to at least automate this within the Python interface. Johan > Garth > > _______________________________________________ > Mailing list: https://launchpad.net/~dolfin > Post to : dolfin@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dolfin > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : dolfin@lists.launchpad.net Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
