-
Notifications
You must be signed in to change notification settings - Fork 383
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
ELM cmake configuration cannot find load files in FindPETSc.cmake, when 'CLM_USE_PETSC' is TRUE #3316
Comments
@jqyin Since I don't have access to ORNL CADES, can this be assigned to you? |
Do you have to be on ORNL CADES to reproduce the problem? We don't officially support that platform. |
@rljacob No. I think that, for whatever reason to use PETSc libraries available in any platform, it's not going to work with cmake. |
Please share the create_newcase command and other steps to reproduce the problem. |
|
|
I'm trying to use PETSc library for coupling PFLOTRAN to ELM. There was no specific create_new_case option for this. |
In #3257, the namelist_definition_drv.xml also needed to be updated. Change sst_aquap11 to sst_aquap_constant. Test suite: Test baseline: Test namelist changes: Tested using QPRCEMIP compset Test status: [bit for bit, roundoff, climate changing] Fixes [CIME Github issue #] none (issue was opened in ESCOMP/CAM as issue 39, but discovered the error was in cime) User interface changes?: Update gh-pages html (Y/N)?: Code review:
After ELM build switches from make to cmake, when 'CLM_USE_PETSC' is TRUE, the cmake configuration cannot successfully find PETSc package. The error message is like:
I think it's because the cmake module files for PETsc package were not ALL copied from Jed Brown's (see: https://github.com/jedbrown/cmake-modules). And some minor edits in cime/src/CMake/FindPETSc.cmake are also needed. So fixes, tested on ORNL CADES, may be like in branch:
fmyuan/lnd/elm-pflotran
commit: 56557334afd8474e68c7b7289e018b2d42dd9b7d
The text was updated successfully, but these errors were encountered: