Update components.yaml to match GEOSgcm v10.22.1 (and update CI) #543
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 ESMA_env, ESMA_cmake, and MAPL in the GEOSldas to match GEOSgcm v10.22.1. The changes are:
parallel_build.csh
(v3.13.0)Of these, the ESMA_cmake is needed for build issues as GMAO_Shared
main
needs this version.Note that there is a chance the MAPL update could be sort-of non-zero-diff. The issue is that Ops found some lats and lons in history output were of the sort of "6.500000000001" instead of "6.5". This MAPL update "fixes" that, and comparators like
nccmp
will see this as a difference. The data is zero-diff, but the lats and lons are not.