-
Notifications
You must be signed in to change notification settings - Fork 322
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
Make "Bytnerowicz" the default nfix_method for clm6 #2972
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -524,9 +524,9 @@ attributes from the config_cache.xml file (with keys converted to upper-case). | |
<!-- The default filenames are given relative to the root directory | ||
for the CLM2 data in the CESM distribution --> | ||
<!-- Plant function types (relative to {csmdata}) --> | ||
<paramfile phys="clm6_0" >lnd/clm2/paramdata/ctsm60_params.c241119.nc</paramfile> | ||
<paramfile phys="clm5_0" >lnd/clm2/paramdata/clm50_params.c241119.nc</paramfile> | ||
<paramfile phys="clm4_5" >lnd/clm2/paramdata/clm45_params.c241119.nc</paramfile> | ||
<paramfile phys="clm6_0" >lnd/clm2/paramdata/ctsm60_params_nfix.c241119.nc</paramfile> | ||
<paramfile phys="clm5_0" >lnd/clm2/paramdata/clm50_params_nfix.c241119.nc</paramfile> | ||
<paramfile phys="clm4_5" >lnd/clm2/paramdata/clm45_params_nfix.c241119.nc</paramfile> | ||
|
||
<!-- ================================================================== --> | ||
<!-- FATES default parameter file --> | ||
|
@@ -1267,7 +1267,7 @@ attributes from the config_cache.xml file (with keys converted to upper-case). | |
ic_ymd="18500101" sim_year="1850" do_transient_pfts=".false." use_excess_ice=".true." | ||
ic_tod="0" glc_nec="10" use_crop=".true." irrigate=".false." | ||
phys="clm6_0" | ||
>lnd/clm2/initdata_esmf/ctsm5.3/ctsm53n04ctsm52028_f09_g17_BgcCrop_exice_pSASU.clm60.r.0161-01-01.nc | ||
>lnd/clm2/initdata_esmf/ctsm5.3/ctsm53019_f09_BNF_pSASU.clm2.r.0161-01-01-00000.nc | ||
</finidat> | ||
<!-- Corresponding ne30 --> | ||
<finidat hgrid="ne30np4.pg3" mask="tx2_3v2" use_cn=".true." use_cndv=".false." use_fates=".false." | ||
|
@@ -1409,7 +1409,7 @@ attributes from the config_cache.xml file (with keys converted to upper-case). | |
ic_ymd="20000101" sim_year="2000" use_excess_ice=".true." | ||
ic_tod="0" glc_nec="10" use_crop=".true." irrigate=".true." | ||
phys="clm6_0" use_init_interp=".true." | ||
>lnd/clm2/initdata_esmf/ctsm5.3/ctsm53n04ctsm52028_f09_g17_BgcCrop_exice_hist.clm60.r.2000-01-01.nc | ||
>lnd/clm2/initdata_esmf/ctsm5.3/ctsm53019_f09_BNF_hist.clm2.r.2000-01-01-00000.nc | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Questions regarding the finidat updates:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure we'll end up creating ne30 and f19 initial conditions with this file, as Linnia is going to have new suggestions from the PPE soon. Instead, maybe we point to the f09 initial conditions and set init_interp = true for other resolutions? |
||
</finidat> | ||
<finidat hgrid="ne30np4.pg3" maxpft="79" mask="tx2_3v2" use_cn=".true." use_cndv=".false." use_fates=".false." | ||
ic_ymd="20000101" sim_year="2000" use_excess_ice=".true." | ||
|
@@ -1894,6 +1894,7 @@ lnd/clm2/surfdata_esmf/NEON/ctsm5.3.0/surfdata_1x1_NEON_TOOL_hist_2000_78pfts_c2 | |
<freelivfix_slope_wet use_fun=".true." use_cn=".true.">0.0006d00</freelivfix_slope_wet> | ||
|
||
<nfix_method>Houlton</nfix_method> | ||
<nfix_method phys="clm6_0">Bytnerowicz</nfix_method> | ||
|
||
<br_root>0.83d-06</br_root> | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
paramfile = '$DIN_LOC_ROOT/lnd/clm2/paramdata/ctsm60_ciso_cwd_hr_params.c241119.nc' | ||
paramfile = '$DIN_LOC_ROOT/lnd/clm2/paramdata/ctsm60_ciso_cwd_hr_params_nfix.c241119.nc' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @wwieder pls review this change, also. For this one I had to generate the new file, so could you check my work given past snafus that we've had with paramfiles? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. sorry, what am I checking for with this file? |
||
hist_fincl1 = 'CWDC_HR','C13_CWDC_HR','C14_CWDC_HR','CWD_HR_L2','CWD_HR_L2_vr','CWD_HR_L3','CWD_HR_L3_vr' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wwieder please review this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to add nfix to the title of the parameter file? This seems unusual to me? Also, do we typically have the same default parameter list for each physics version? This is naive on my part.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @wwieder I'd nix nfix in the name of the file. We make so many changes to paramfiles you can't keep adding the list of new things to the filenames.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The values of the parameters are different for each physics version. Hence, we need to have a different parameter file for each physics version. In CESM3.0 we are likely to have two parameter files for clm6_0, one for coupled and one for CRUJRA.
Does that answer your question?