Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epetra.PyComm() broken on Debian #301

Closed
wd15 opened this issue Sep 19, 2014 · 1 comment
Closed

Epetra.PyComm() broken on Debian #301

wd15 opened this issue Sep 19, 2014 · 1 comment

Comments

@wd15
Copy link
Contributor

wd15 commented Sep 19, 2014

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

@wd15
Copy link
Contributor Author

wd15 commented Sep 19, 2014

Workaround committed in r5107, r5108, r5109, r5110.

Trac comment by wd15 on 01-13-2012 at 16:05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants