ctsm5.4.027: Important coupled model final answer changes: param file and n_melt_glcmec#3810
ctsm5.4.027: Important coupled model final answer changes: param file and n_melt_glcmec#3810ekluzek wants to merge 11 commits intoESCOMP:masterfrom
Conversation
Merge b4b-dev to master Purpose and description of changes ---------------------------------- Merge b4b-dev to master: Important things coming in: - mizuRoute! (NOTE: mizuRoute is a River model (ROF in the CESM context) that can be run in place of MOSART or RTM) - Documentation updates - Move a few namelist parameters to the parameter file - move of X components for nuopc - mksurfdata_esmf for Gnu compiler - scripts for CRUJRA forcing to handle Antarctica/Greenland - SpinupStablity script update to handle FATES and SE grids - Update cdeps for access to CMIP7 CO2 - Tests for FATES Tree Recruitment Scheme (TRS) Main grids to use with mizuRoute: Default mizuRoute grids will use the half degree land-only mizuRoute grid that is the same resolution as the MOSART grid. - 5x5_amazon_r05 - is the small Amazon region for testing - 5x5_amazon_rHDMA - is the small Amazon region using the HDMA for mizuRoute - nldas2_nldas2_rUSGS_mnldas2 - is the Continental US grid with USGS Geospatial Fabric - f09_f09_rHDMA_mg17 - is the 2 degree grid with the medium resolution HDMA grid - f09_f09_rHDMAlk_mg17 - is the 2 degree grid with the medium resolution HDMA grid that includes lakes - hcru_hcru_rMERIT_mt13 - is the half degree grid with the high resolution MERIT grid Standard case to run with mizuRoute: grid=f09_f09_rHDMAlk_mg17 compset=I2000Clm60SpMizGs
…certain CLM compsets" This reverts commit 220a9b1.
… removed from testmods
|
Ran testing last night. I have some unexpected fails on Derecho to figure out, for mizuRoute tests. It looks like Izumi is good other than some current fails to read baselines. I also need to go over all the DIFF's and make sure they are correct. |
slevis-lmwg
left a comment
There was a problem hiding this comment.
Thank you @ekluzek. I'm approving and simply asking a few questions to make sure that I follow.
| <!-- For clm4_5, make this effectively unlimited --> | ||
| <int_snow_max phys="clm4_5" >1.e30</int_snow_max> | ||
|
|
||
| <n_melt_glcmec phys="clm6_0" >1.0d00</n_melt_glcmec> |
There was a problem hiding this comment.
I thought that we might have applied this value only in coupled cases, but I see how it probably makes more sense to make the change for all clm6.
There was a problem hiding this comment.
Yeah, since the CISM folks want it changed, I think it should be changed for both coupled and uncoupled. That way any offline spinup with CISM will be consistent with coupled. And in general we want uncoupled cases to be the same as coupled unless there are really good reasons not to.
cime_config/testdefs/testmods_dirs/clm/ExcessIceStartup_output_sp_exice/user_nl_clm
Show resolved
Hide resolved
|
From what I can tell, the mizuRoute cases that didn't work were just a random fluke? I'm not figuring anything out that can reliably trigger it to fail. |
|
NEON Clm60 cases are using the 2015 file rather than the 2000 file, because the date is closer. So this needs to be adjusted so that doesn't happen. |
|
Fates tests are showing differences as well, because I didn't bring in ctsm5.4.026 when I started the testing. In looking through the Izumi tests that differ from baseline, they all (other than the NEON and Fates ones) are correct. For clm6_0 n_melt_glcmec changes and the LndTuning mode test also uses the coupled param file as it should. |
Description of changes
Some important final answer changes needed for the coupled model to get the right parameter file and to set n_melt_glcmec=1 for clm6_0.
Also use the 2015 finidat file for SSP future scenarios.
Specific notes
Contributors other than yourself, if any: @slevis-lmwg
CTSM Issues Fixed (include github issue #):
Fixees #3799
Fixes #3824
Fixes #3826
Are answers expected to change (and if so in what way)? Yes!
coupled model and clm60cam7LndTuning mode tests change answers due to parameter file
clm6_0 cases change answers because of change in n_melt_glcmec
SSP cases change answers for cases where the finidat file changes
Any User Interface Changes (namelist or namelist defaults changes)? Yes
n_melt_glcmec is 1 for clm6_0
paramfile for clm6_0_cam7.0 changes
2015 finidat file for SSP cases starting in 2015
Does this create a need to change or add documentation? Did you do so? No No
Testing performed, if any: Will do regular