You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The packages version of Trilinos seems to be broken on Debian. See http://help.lockergnome.com/linux/Bug-620802-python-pytrilinos-fails-work--ftopict535197.html. The work around is to import mpi4py prior to using trilinos. This can be implemented right away in fipy/tools/init.py simply by testing the os version and trilinos version and doing the mpi4py import prior to the trilinos import.
The other question is why trilinos is imported at all if the trilinos solvers are not being used. I think this is to do with the parallel and serial comms. There is some circular logic there that I wasn't sure about last time I checked it. I wasn't clear on how to fix this.
Imported from trac ticket #420, created by wd15 on 01-13-2012 at 12:26, last modified: 01-13-2012 at 16:05
The text was updated successfully, but these errors were encountered:
The packages version of Trilinos seems to be broken on Debian. See http://help.lockergnome.com/linux/Bug-620802-python-pytrilinos-fails-work--ftopict535197.html. The work around is to import mpi4py prior to using trilinos. This can be implemented right away in fipy/tools/init.py simply by testing the os version and trilinos version and doing the mpi4py import prior to the trilinos import.
The other question is why trilinos is imported at all if the trilinos solvers are not being used. I think this is to do with the parallel and serial comms. There is some circular logic there that I wasn't sure about last time I checked it. I wasn't clear on how to fix this.
Imported from trac ticket #420, created by wd15 on 01-13-2012 at 12:26, last modified: 01-13-2012 at 16:05
The text was updated successfully, but these errors were encountered: