Update to fvdycore geos/v2.7.0 #696
Merged
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
sdrabenh
approved these changes
Nov 7, 2023
This was referenced Nov 9, 2023
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 GEOS to use fvdycore geos/v2.7.0. This is zero-diff for GEOSgcm as it adds support for a by-default-off new way of computing coordinates.
This is a companion PR to GEOS-ESM/FVdycoreCubed_GridComp#258 and GEOS-ESM/GEOSgcm_App#535. Both of these use the new namelist parameter added in fvdycore geos/v2.7.0. But we can't add that flag until we have the Fortran to support it.
Thus, we get this in first, then we can dribble in the other two PRs.