update CMEPS to allow bilinear ATM<->WAV mapping for global coupled application; utilize custom restart names for WW3 (was #1684) #1685
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
Changes the mapping of state fields between ATM and WAV for the coupled model to use bilinear with nearest-source-to-destination filling.
A test case was run using the
cpld_control_p8
test for 24 hours with and w/o this change. The following figure shows the difference inU10M
along ~62S, from 90W:40W imported by the WAV model with the current mapping (mapnstod_consf
, black line) vs the change in this PR (mapbilnr_nstod
, red line).The impact on the
Z0
imported by the ATM at ~0.5S,6E (on the coast of Brazil, where a large difference inZ0
is seen) for the current mapping (red) vs this PR (black) is shown belowIn the bmark test, the difference in
Z0
imported by the ATM on tile 1 (scaled by 1.0e4) after 6 hours is shown belowTop of commit queue on: TBD
Input data additions/changes
Anticipated changes to regression tests:
This will change baselines for all coupled tests using ATM-WAV coupling. HAFS wave tests do not change since their mapping is mapfillv_bilnr and does not change.
Full RTs on cheyenne show the following:
GNU:
INTEL:
RegressionTests_cheyenne.gnu.log
RegressionTests_cheyenne.intel.log
Subcomponents involved:
Combined with PR's (If Applicable):
Commit Queue Checklist:
Linked PR's and Issues:
Testing Day Checklist:
Testing Log (for CM's):