changes needed for CDEPS PR #213 #341
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
jedwards4b
approved these changes
Jan 31, 2023
|
@uturuncoglu - the CDEPS PR must be accompanied by this PR. Does it fit into your schedule to review and test it over the next day or two? |
uturuncoglu
approved these changes
Feb 1, 2023
|
@mvertens I am in ESMF metting. I could test it today with UFS. |
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.
Description of changes
changes needed for CDEPS PR #213
Specific notes
Changes needed to enable flexible import to data ocean to be available in mediator history files
Contributors other than yourself, if any: None
CMEPS Issues Fixed (include github issue): #340
Are changes expected to change answers? (specify if bfb, different at roundoff, more substantial) No - bfb
Any User Interface Changes (namelist or namelist defaults changes)? None
Testing performed
Verified bfb for docn test cases.
Verified that SMS_Ld5.f09_g17.B1850G.cheyenne_intel.allactive-cism-test_coupling and
ERP_Ln9_Vnuopc.ne30_ne30_mg17.F2000climo.cheyenne_intel.cam-outfrq9s were bfb compared to cesm2_3_beta11
Hashes used for testing: