dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Tue, Mar 22, 2011 at 06:29:23PM +0000, 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. Any other suggestions?

I think it should be possible to control the order. I would very much
like to avoid explicit init functions.

Can you create a simple test that goes wrong and maybe I can look at
it (but not tonight).

--
Anders


--
Anders


> Garth
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help   : https://help.launchpad.net/ListHelp