Update components to match GEOSgcm v11 as of 2025-Sep-19#836
Merged
gmao-rreichle merged 1 commit intodevelopfrom Sep 24, 2025
Merged
Update components to match GEOSgcm v11 as of 2025-Sep-19#836gmao-rreichle merged 1 commit intodevelopfrom
gmao-rreichle merged 1 commit intodevelopfrom
Conversation
Contributor
|
All tests passed. |
Member
Author
Hooray! Thanks for testing. I'll undraft. |
gmao-rreichle
approved these changes
Sep 24, 2025
This file contains hidden or 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
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 PR updates the components in GEOSldas to match that of GEOSgcm
mainas of 2025-Sep-19. This brings in a few things:esma_mpirunI've also updated some CI to test if all this works.
The most important part of this is MAPL 2.59.1. That is important because it provides support for ESMF v9. Now, MAPL2 (and thus GEOSgcm, GEOSldas, etc.) does not require ESMF v9 but MAPL3 does. But, having support to use ESMF v9 allows us to keep around a single set of Baselibs/ESMA_env.
Second, #835 by @biljanaorescanin trumps this in terms of GEOS_Util, but I decided to just echo GEOSgcm
mainThird, as I know @gmao-rreichle will probably spot it, ESMA_env went from v4 to v5. Now, that difference is because ESMA_env v5 has Baselibs v8 which includes FMS (which doesn't matter to GEOSldas).
I'm going to keep this draft until it can be tested by @biljanaorescanin or others. But I wanted to get this in to see what CI does.