bugfix in boundary conditions for coupled T3MOM6 option #861
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
biljanaorescanin
added
0 diff
gmao-rreichle
approved these changes
Nov 29, 2023
sdrabenh
approved these changes
Nov 30, 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.
Boundary conditions package for option
T3MOM6should use input filesMOM6/540x458but due to typo we were trying to useMOM6/580x458which produce code to fail since i's and j's information are picked from that line.Somehow during testing this was missed and this is a bug fix.
This PR is zero diff for AGCM.
This code is run with boundary conditions package run, so its bug fix for boundary conditions package for MOM6 grid option T3MOM6 in package.
@yvikhlya @sanAkel @gmao-rreichle