v11: Update to ESMA_env v4.32.0, ESMA_cmake v3.54.0 #804
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mathomp4
added
the
0 diff
mathomp4
changed the title
mathomp4
changed the title
mathomp4
added
Contingent - DNA
mathomp4
changed the title
6 tasks
mathomp4
changed the title
mathomp4
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update GEOSgcm to use ESMA_env v4.32.0
The ESMA_env update moves GEOS to use Baselibs 7.27.0 which mainly updates to GFE v1.16.0 which is needed for MAPL development. It also grabs ESMF 8.7.0.
But, GFE v1.16 seems to have a weird issue with Intel 2021.6. So, on SLES15 at NCCS, NAS, and GMAO desktops, we move to Intel ifort 2021.13 as our compiler. We also move to Intel MPI 2021.13 as the MPI stack at NCCS and at GMAO. (NOTE: The model will still run on SLES12 even with Intel ifort 2021.6, but
make testswill fail in MAPL.)It also has updates for NAS as well as changing the default build processor at NCCS to Milan.
We also update to ESMA_cmake v3.54.0 which has updates for Python 3.12 as well as running
mepo statusat build time and capturing this output.NOTE: It looks like this is zero-diff in regards to the state (aka the restarts), but it is non-zero-diff in regards to the history output. It looks like round-off-ish, but... 🤷🏼