-
Notifications
You must be signed in to change notification settings - Fork 371
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
Fix MPAS standalone compile issues #6134
Fix MPAS standalone compile issues #6134
Conversation
With these changes, MPAS-Ocean standalone compiles with gnu debug on chrysalis and chicoma and passes the nightly test suite on both. I can successfully compile mpas-seaice with gnu debug. I was not able to compile MALI, but I'm not familiar with it, so probably did it wrong. |
This PR also compiles MPAS-Ocean with intel debug on chrysalis and passes the nightly test suite. MALI compiles successfully with intel on chrysalis but not gnu. |
I'm also not able to build MALI on Chrysalis with gnu. I'm using a compass load script with albany support. When I run:
I see:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested the compass pr
suite on Chrysalis with Intel and OpenMPI using this branch, and all tests ran successfully.
I confirmed that E3SM builds are unaffected. This passes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Passes the polaris
mpas-seaice single_column test suite.
FYI, I was able to compile the standalone MPAS-O with gnu on Perlmutter and my Mac. Some standalone test cases were successfully terminated. |
I checked LISIO, since that one tests MALI within E3SM. It passes:
|
I successfully compiling MALI on Anvil with gnu and mvapich and without Albany. I'm getting a compass error trying to set up a fresh compass env on Perlmutter, but using an existing @mark-petersen , @xylar , should we be worried about the MALI compile problems you are both seeing? |
@matthewhoffman I tested commit 09491ec, which was the last commit working before stand-alone compile issues were introduced. The MALI problem existed at that point, i.e. this command on chrysalis
fails in exactly the same way as it does with this PR. So the issue seems to be unrelated. Since you were able to compile on Anvil, and we compiled MALI on chrysalis with intel, I think we should proceed with the fixes in this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on @mark-petersen's information, I'm approving this based on the MALI compilation tests that pass and that the ones that don't are a problem pre-existing this PR.
…#6134) Fix MPAS standalone compile issues These two small changes allow MPAS components to compile in stand-alone mode. It should not affect E3SM compile or simulations. The fixes are: * A missing endif was added to the Makefile * A redundant corelist declaration was removed from mpas.F because it was added to mpas_subdriver.F in PR Introduce MOAB coupler interfaces and update moab driver #5979, and the subdriver is used by mpas.F. These fixes should work for ocean, sea ice, and MALI cores. Fixes #6133 Fixes #6138 [BFB]
Passes:
merged to next |
merged to master |
These two small changes allow MPAS components to compile in stand-alone mode. It should not affect E3SM compile or simulations. The fixes are:
endif
was added to the Makefilempas.F
because it was added tompas_subdriver.F
in PR Introduce MOAB coupler interfaces and update moab driver #5979, and the subdriver isused
bympas.F
.These fixes should work for ocean, sea ice, and MALI cores.
Fixes #6133
Fixes #6138
[BFB]