-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
B1850 compsets are failing cesm2_3_alpha17d and cesm2_3_alpha17e #2520
Comments
The B1850 compset used in the test is: 1850_CAM60_CLM50%BGC-CROP_CICE_POP2%ECO_MOSART_CISM2%GRIS-NOEVOLVE_WW3_SESP_BGC%BDRD user_nl_clm hist_dov2xy = .true.
hist_ndens = 1
hist_nhtfrq =-24
hist_mfilt = 1 It also does something similar for MOSART and RTM, which shouldn't matter. Other user_nl_* settings shouldn't matter. The CLM_ XML settings also seem to be fine. There are no f09 tests for 1850Clm50BgcCropG in aux_clm, also no tests for it in ctsm_sci. The tests that are in aux_clm: ERP_D_Ld5.f10_f10_mg37.I1850Clm50BgcCropG.derecho_gnu.clm-glcMEC_changeFlags (but none of those might catch a problem for f09) Tests that I DO THINK should have caught this: LII2FINIDATAREAS_D_P256x2_Ld1.f09_g17.I1850Clm50BgcCrop.derecho_intel.clm-default The first two passed, and the last two failed in the build step, and the second explicitly turns interp on. So the only one to catch it would be the first one: The unexpected differences in the lnd_in namelist that I see are: < finidat = '/glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/initdata_map/clmi.B1850Clm50BgcCrop.0161-01-01.0.9x1.25_gx1v7_simyr1850_c200729.nc'
---
> finidat = '/glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/initdata_esmf/ctsm5.2/clmi.I1850Clm50BgcCrop-ciso.1366-01-01.0.9x1.25_gx1v7_simyr1850_c240223.nc'
20c21
< glc_do_dynglacier = .true.
---
> glc_do_dynglacier = .false. So the B1850 case is using an incorrect finidat file, and needs to be updated to use the ctsm5.2.0 one. I think that might be in CESM rather than in CTSM, but I'll need to track that for sure. I'm also perplexed by the dynglacier setting. |
The glc_do_dynglacier setting is expected because of the compset with active CISM. It looks like there are bunch of settings in namelist_defaults that need to have the
attribute added in. In terms of testing it turns out there are very few tests that are being done that don't need use_init_interp=TRUE. There are only finidat files that could do that for f09 and f19 as well as a few SE grids (ne0np4.*.ne30x8, and ne120np4.pg3). I think those are only being tested for clm6_0 physics. The ctsm_sci test list should probably do more tests at clm5_0 because of this sort of thing. |
Oh, the reason that the finidat files do NOT match is because of the LND_TUNING_MODE. And that's part of the problem here that we should have some more tests for f09 and f19 that use LND_TUNING_MODE set to CAM6 (and for a few different CLM physics options). So I think everything is back to making sense for me now... |
An important note here is that one issue here is that B and F compsets are testing with clm5_0 and NOT clm5_1. clm5_1 is what will be used for the coupled simulations in this tag. As such these fails do NOT necessarily need to hold up the cesm2_3_beta17 tag. @wwieder we've had some email about this with @briandobbins and @fischer-ncar. Brian is also going to ask @dlawrenncar. |
Manually examining the CAM testlist I see the following...
Hence, for CAM testing right now we need I1850Clm50Sp(for CAM6), I2000Clm50Sp (for CAM6), I2010Clm50Sp (for CAM6), IHistClm50BgcCrop (for CAM6), and IHistClm50BgcCrop (for CAM6). And the science supported resolutions are f09 and f19. Also note that WACCM uses *_NCPL of 288, which shouldn't be a problem in our testing, but also something Also note that CAM FHist compsets start at a variety of different years. We don't necessarily need to start at all these different years, but we do need to make sure they will work. <value compset="HIST_CAM">1979-01-01</value>
<value compset="HIST_CAM60%WCTS_CLM50%BGC-CROP">1950-01-01</value>
<value compset="HIST_CAM40%WX">2000-01-01</value>
<value compset="HIST_CAM60%WCMD">2005-01-01</value>
<value compset="HIST_CAM60%WCMD%SDYN" grid="a%1.9x2.5">1980-01-01</value>
<value compset="HIST_CAM60%WCSC">1850-01-01</value>
<value compset="HIST_CAM60%CCTS[12]">2010-01-01</value>
<value compset="HIST_CAM60%GEOSCHEM">2015-01-01</value>
<value compset="HIST_CAM60%CCTS[12]" grid="a%ne0np4CONUS">2013-01-01</value>
<value compset="HIST_CAM60%CVBSX">1995-01-01</value>
<value compset="HIST_CAM60%CFIRE">1995-01-01</value> Since, HIST compsets have to use use_init_interp=.true. these later startup years should be fine. As long as I1850 and IHist work. So the above compset list is still OK. When #2498 comes in, we'll need to reassess this a bit. Once, CAM is updated to use CLM60 physics in it's testlist we should update tests to work with clm6_0_cam7.0. Also I assume that ne30np4.pg3 will be a required science support resolution for CAM. |
For CESM testing CLM51%BGC-CROP and CLM50%BGC-CROP (for cam6.0) at 1850 and HIST compsets are important. So IHistClm50BgcCropG, IHistClm51BgcCropG, I1850Clm50BgcCropG, I1850Clm51BgcCropG at f09, f19, ne30pg3_t061, and ne30pg3_t232 cover current testing. And updating to clm6_0_cam7.0 when CESM does is also needed. |
Brief summary of bug
@fischer-ncar found tests such as SMS_Ld7.f09_g17.B1850.derecho_intel.allactive-defaultio are failing in cesm2_3_alpha17d and cesm2_3_alpha17e because the finidat files need to have use_init_interp=TRUE and for some reason this isn't happening.
General bug information
CTSM version you are using: ctsm5.2.0
Does this bug cause significantly incorrect results in the model's science? No
Configurations affected: f09 @ B1850
Details of bug
Important details of your setup / configuration so we can reproduce the bug
In cesm2_3_alpha17d and cesm2_3_alpha17e
Important output or errors that show the problem
The text was updated successfully, but these errors were encountered: