Coupled GraphCast #11
Open
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
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 adds capability to handle REPLAY ocean, land, and ice dataset in the GraphCast architecture. A major portion of the codebase update deals with handling the vertical levels in the oceans, which is labeled as "z_l" the REPLAY dataset -- the cell center of the replay vertical levels. Note, that REPLAY interpolates the time-varying ALE MOM6 vertical coordinate to fixed vertical levels, and therefore "z_l" is static in time. The other components "land" and "ice" do not have a stacked 3D dataset and the vertical levels are treated as separate 2D variables. So, handling those is pretty straightforward.
Currently, the ocean vertical level is hard-coded as "z_l" and the atmospheric vertical coordinate is hard-coded as "level", however I believe these should be user specificied and can be included in kwargs. But this UFS-spcific fork of graphcast anyway, so I don't think this is super important for our purposes.