-
Notifications
You must be signed in to change notification settings - Fork 31
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
PFlotran engine needs to be updated to a more recent version #17
Comments
After talking with Glenn, who says that the chemistry interface has been stable for a while, I think we should target PFlotran commit cfa0b8d (the HEAD of the repo at the time of this message). |
I am ok with upgrading the pflotran interface. I believe this would also involve updating the input files of the tests. As far as Petsc 3.6, I would like to make sure that Crunch also works with 3.6 so that we don't have to deal with two petsc's for Alquimia. |
Ok. I haven't prioritized this yet, but it's likely that I could produce an updated version of the PFlotran engine before the IDEAS xSDK release in February. If/when you get a chance to test Crunch with PETSc 3.6, just let me know if you run into any issues, and I'll be happy to help out. |
There are branches that work with petsc 3.6. It is trivial for crunch, but On Wed, Jan 20, 2016 at 9:56 AM, Jeffrey Johnson [email protected]
|
This is less urgent than it was before. Alquimia now works with the 3.6 and development versions of PETSc. |
The version of the PFlotran reaction library we're using is now quite old, and uses an older version of PETSc (3.5 instead of 3.6). Moreover, it looks like an odd interaction between Alquimia and that version of PFlotran prevents shared library builds of Alquimia from working properly (see #16).
We need to establish a newer version of the reaction library to link against (hopefully a release instead of a hash of pflotran-dev) and modify the Alquimia PFlotran engine code accordingly, making sure that shared library builds work on Mac and Linux.
The text was updated successfully, but these errors were encountered: