-
Notifications
You must be signed in to change notification settings - Fork 383
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2066 from billsacks/glc2ocn_separate_liq_ice
Separate liq and ice in glc2ocn mapping, and fix glc2ocn mapping bug Two changes in this PR: (1) Main change: Separate the mapping of liquid and ice runoff from glc2ocn. This parallels a similar change made for the rof2ocn mapping. This is needed in CESM with POP, because the ice runoff still needs smoothing, but the liquid runoff should now be nearest neighbor to coastal points without smoothing. (Fixes ESMCI/cime#1940) In addition to making the code changes to support this separation, I have regenerated all glc2ocn mapping files for CESM (using commit b013b57). The liquid mapping files are completely different from before (now nearest-neighbor to coastal points, rather than nearest-neighbor with smoothing). The ice mapping files are slightly different from before because of a slightly changed process for generating these files (now nearest-neighbor to coastal points followed by smoothing, rather than nearest-neighbor to any point followed by smoothing; also, the mappings to gx3v7 now use rmax=500000 rather than 300000 to agree with rof -> ocn maps). For ACME, I point to the same mapping files for liquid and ice; I haven't changed these mapping files (similarly to what's done for rof2ocn mapping files). (2) Small but important change, which changes answers substantially for cases with a 2-way-coupled, evolving ice sheet: Do NOT use normalization in doing glc2ocn runoff mapping. (Fixes ESMCI/cime#2063) This bug only affects runs with a 2-way-coupled, evolving ice sheet (which, at least in CESM, only involves runs done by a few members of the Land Ice Working Group; I'm not sure about E3SM). I have done a quick investigation of the impact of this bug. I found that (for a run with 4-km Greenland and gx1v7 ocean) the runoff reaching the ocean was too low by a factor of 2-3. However, it looks like there could be significant spatial variability in this bug's impact - so the actual impact would depend on exactly where the runoff (calving and basal melt) is generated. In addition, the impact of this bug would differ with different glc and ocn resolutions. Test suite: scripts_regression_tests on yellowstone Also ran a bunch of J compset (all-active except data atmosphere) tests in CESM: see comment below for details. Test baseline: n/a Test namelist changes: splits glc2ocn_rmapname into glc2ocn_liq_rmapname and glc2ocn_ice_rmapname; splits glc2ocn_rmaptype into glc2ocn_liq_rmaptype and glc2ocn_ice_rmaptype. Test status: climate changing - just for cases with 2-way-coupled, evolving ice sheet (in CESM, this means compsets that have CISM2%EVOLVE) Fixes ESMCI/cime#1940 Fixes ESMCI/cime#2063 User interface changes?: Splits GLC2OCN_RMAPNAME xml variable into GLC2OCN_LIQ_RMAPNAME and GLC2OCN_ICE_RMAPNAME, and similarly for GLC2OCN_RMAPTYPE Update gh-pages html (Y/N)?: N Code review:
- Loading branch information
Showing
5 changed files
with
104 additions
and
22 deletions.
There are no files selected for viewing
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
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
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
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
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