dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #20862
[Bug 705401] [NEW] When PyTrilinos is imported after dolfin, bad things happen
Public bug reported:
When using PyTrilinos (ML in particular), the order of imports is
important. If dolfin is imported first, it crashes at exit, and there
are problems also with constructing preconditioners etc.
It looks like it has to do with MPI initialisation, but I haven't looked
at it closely.
A simple workaround may be to try an import ML in dolfin/__init__.py
(just import, not expose) so that it gets initialised. I don't know if
the performance hit is worth it. It would of course be better to find a
proper fix.
Otherwise, it's nice to have it documented here. For google::
>>> import dolfin
>>> from PyTrilinos import ML
>>> exit()
*** An error occurred in MPI_Finalize
*** after MPI was finalized
*** MPI_ERRORS_ARE_FATAL (your MPI job will now abort)
[rodin:17864] Abort after MPI_FINALIZE completed successfully; not able to guarantee that all other processes were killed!
** Affects: dolfin
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DOLFIN
Team, which is subscribed to DOLFIN.
https://bugs.launchpad.net/bugs/705401
Title:
When PyTrilinos is imported after dolfin, bad things happen
Status in DOLFIN:
New
Bug description:
When using PyTrilinos (ML in particular), the order of imports is
important. If dolfin is imported first, it crashes at exit, and there
are problems also with constructing preconditioners etc.
It looks like it has to do with MPI initialisation, but I haven't
looked at it closely.
A simple workaround may be to try an import ML in dolfin/__init__.py
(just import, not expose) so that it gets initialised. I don't know if
the performance hit is worth it. It would of course be better to find
a proper fix.
Otherwise, it's nice to have it documented here. For google::
>>> import dolfin
>>> from PyTrilinos import ML
>>> exit()
*** An error occurred in MPI_Finalize
*** after MPI was finalized
*** MPI_ERRORS_ARE_FATAL (your MPI job will now abort)
[rodin:17864] Abort after MPI_FINALIZE completed successfully; not able to guarantee that all other processes were killed!
Follow ups
-
[Bug 705401] Re: When PyTrilinos is imported after dolfin, bad things happen
From: Garth Wells, 2011-03-23
-
[Bug 705401] Re: When PyTrilinos is imported after dolfin, bad things happen
From: Garth Wells, 2011-03-23
-
[Bug 705401] Re: When PyTrilinos is imported after dolfin, bad things happen
From: Garth Wells, 2011-01-23
-
[Bug 705401] Re: When PyTrilinos is imported after dolfin, bad things happen
From: Johan Hake, 2011-01-23
-
[Bug 705401] Re: When PyTrilinos is imported after dolfin, bad things happen
From: Joachim Haga, 2011-01-22
-
[Bug 705401] Re: When PyTrilinos is imported after dolfin, bad things happen
From: Joachim Haga, 2011-01-22
-
[Bug 705401] Re: When PyTrilinos is imported after dolfin, bad things happen
From: Joachim Haga, 2011-01-22
-
[Bug 705401] Re: When PyTrilinos is imported after dolfin, bad things happen
From: Joachim Haga, 2011-01-22
-
Re: [Bug 705401] [NEW] When PyTrilinos is imported after dolfin, bad things happen
From: Garth Wells, 2011-01-20
-
[Bug 705401] [NEW] When PyTrilinos is imported after dolfin, bad things happen
From: Joachim Haga, 2011-01-20
References