You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or 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
Point to new mapping files for r05 <-> f10 mapping
The new mapping files were generated by @mvertens with a recent version
of ESMF_RegridWeightGen, with '--ignore_unmapped -m conserve'.
The new rof -> lnd map should fix the issue with the old map, that
mapping a 1 field from rof -> lnd without normalization leads to non-1
values on the destination.
Test suite: Cherry-picked the change into the cime version used in ctsm master, then ran SMS_D_Ld3.f10_f10_musgs.I1850Clm50BgcCrop.cheyenne_intel.clm-default
with comparison against master.
Test baseline: ctsm1.0.dev052
Test namelist changes: lnd2rof_fmapname, rof2lnd_fmapname
Test status: greater than roundoff, but probably not climate changing;
only changes cases using the f10 grid (just used for testing)
There are differences in the following CLM fields (these are either directly related to the mapped river volume, or depend on it via methane's dependence on total gridcell water volume):
The new mapping files were generated by @mvertens with a recent version
of ESMF_RegridWeightGen, with '--ignore_unmapped -m conserve'.
The new rof -> lnd map should fix the issue with the old map, that
mapping a 1 field from rof -> lnd without normalization leads to non-1
values on the destination.
ResolvesESMCI#3185
I have imported the new files. @fischer-ncar feel free to merge this whenever you're ready, noting that it will change answers for cases using the f10 grid.
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.
Point to new mapping files for r05 <-> f10 mapping
The new mapping files were generated by @mvertens with a recent version
of ESMF_RegridWeightGen, with '--ignore_unmapped -m conserve'.
The new rof -> lnd map should fix the issue with the old map, that
mapping a 1 field from rof -> lnd without normalization leads to non-1
values on the destination.
Test suite: Cherry-picked the change into the cime version used in ctsm master, then ran
SMS_D_Ld3.f10_f10_musgs.I1850Clm50BgcCrop.cheyenne_intel.clm-default
with comparison against master.
Test baseline: ctsm1.0.dev052
Test namelist changes: lnd2rof_fmapname, rof2lnd_fmapname
Test status: greater than roundoff, but probably not climate changing;
only changes cases using the f10 grid (just used for testing)
There are differences in the following CLM fields (these are either directly related to the mapped river volume, or depend on it via methane's dependence on total gridcell water volume):
and in the following cpl fields:
Fixes #3185
User interface changes?: N
Update gh-pages html (Y/N)?: N
Code review: