-
Notifications
You must be signed in to change notification settings - Fork 3
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
n1850.ne30_tn14.hybrid_fatessp.202401031 #51
Comments
@monsieuralok - please use ./xmlchange --append CLM_BLDNML_OPTS="-ignore_warnings" and the finidat used above. |
@monsieuralok - please don't start yet - it turns out that finidat is being set to ' ' |
@monsieuralok - so there is a problem with how finidat can be set for a startup run with FATES. At this point since we are using FATES-SP - please go ahead and let finidat = ' ' and simply do a 20 year run with that setting. I've modified the directions to reflect that. Sorry for all of the confusion. |
@mvertens if we change file components/clm/bld/namelist_files/namelist_defaults_overall.xml and comment line which sets startup type to COLD in case of FATE then we will able to set finidat. That I have tested. |
@monsieuralok - that is right - but after a long discussion today with the CICERO group, we don't want to do that. I've put in a place a temporary fix in CLMBuildNamelist.pm with the following change
and this permits you to keep the the default vallue of clm_start_type for fates to cold. They key issue is that there was no way to set finidat for a startup run with fates. So this temporary hack will fix that. And in the meantime, @rosiealice will talk in more depth with the FATES developers to determine a more sustainable way forwards. In addition, the file that finidat pointed to before is not compatible with ctsm5.3 - so @maritsandstad needs to create another spinup. So for now just having findiat=' ' in this simulation is fine. |
Purpose:
Duplicate of n1850.ne30_tn14.hybrid_fatessp.20241007 but with a fix for DMS in CAM. The goal is to run 20 years.
Description:
limit
when running past 11 years.See memory leak in n1850 case NorESM#550
Description:
user_nl_blom
ICFILE = "/cluster/shared/noresm/inputdata/restart/NOIIAJRAOC20TR_TL319_tn14_ppm_20240816/rest/1775-01-01-00000/NOIIAJRAOC20TR_TL319_tn14_ppm_20240816.blom.r.1775-01-01-00000.nc"
user_nl_cice
ice_ic = "/cluster/shared/noresm/inputdata/restart/NOIIAJRAOC20TR_TL319_tn14_ppm_20240816/rest/1775-01-01-00000/NOIIAJRAOC20TR_TL319_tn14_ppm_20240816.cice.r.1775-01-01-00000.nc"
user_nl_clm
Add the following to user_nl_clm
Compset long name
1850_CAM%DEV%LT%NORESM%CAMoslo_CLM60%FATES-SP_CICE_BLOM%ECO_MOSART_DGLC%NOEVOLVE_SWAV_SESP
Model grid long name
a%ne30np4.pg3_l%ne30pg4.pg3_oi%tnx1v4_r%r05_w%null_z%null_g%gris4_m%tnx1v4
Case directory:
<user_pathname>/n1850.ne30_tn14.hybrid_fatessp.202401031
Code version on github:
Diagnostics:
Compared to NorESM2-MM: https://ns2345k.web.sigma2.no/datalake/diagnostics/ADF/plots/n1850.ne30_tn14.hybrid_fatessp.202401031_10_20_vs_N1850frc2_f09_tn14_20191001_1209_1219/website/index.html
Compared to n1850.ne30_tn14.hybrid_fatessp.202401007:
Output:
/nird/datalake/NS9560K/noresm3/cases/n1850.ne30_tn14.hybrid_fatessp.20241031
Contacts:
@mvertens, @monsieuralok
Extra details:
The text was updated successfully, but these errors were encountered: