Skip to content
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

Move namelist parameters to paramfile #2831

Open
linniahawkins opened this issue Oct 10, 2024 · 5 comments
Open

Move namelist parameters to paramfile #2831

linniahawkins opened this issue Oct 10, 2024 · 5 comments
Assignees
Labels
enhancement new capability or improved behavior of existing capability

Comments

@linniahawkins
Copy link

linniahawkins commented Oct 10, 2024

The PPE team would like to have several parameters that are currently set in the namelist moved to the parameter file:

Jmaxb1 (as a pft dimensioned value, per #2830)
baseflow_scalar
upplim_destruct_metamorph
maximum_leaf_wetted_fraction
interception_fraction
pot_hmn_ign_counts_alpha
decomp_depth_efolding

This is not 100% necessary for us to move forward, our scripting can handle namelist parameter modifications, but it would make things clean and simple.

@linniahawkins linniahawkins added the enhancement new capability or improved behavior of existing capability label Oct 10, 2024
@wwieder
Copy link
Contributor

wwieder commented Oct 10, 2024

Thanks for opening this issue and #2830? What's a useful timeline for these? it may be simple enough to create the parameter file that you can use (he said naively), but then it's 2-weeks until b4b-dev comes to main.

@linniahawkins
Copy link
Author

Neither of these are necessary for the mini-OAAT (October) nor the first latin-hypercube ensemble (November).

#2831 would be convenient to have by November 1 (but not necessary).
#2830 will be necessary for history matching (late November).

@wwieder wwieder added this to the cesm3_0_beta05 milestone Oct 10, 2024
@olyson olyson self-assigned this Oct 16, 2024
@olyson
Copy link
Contributor

olyson commented Oct 16, 2024

I should be able to start this soon.

@olyson
Copy link
Contributor

olyson commented Oct 17, 2024

I find that decomp_depth_efolding is already on the parameter file.

@olyson
Copy link
Contributor

olyson commented Oct 20, 2024

I think transferring baseflow_scalar is problematic because its value depends on the lower_boundary_condition chosen. Similarly, pot_hmn_ign_counts_alpha is a tuning parameter for fire and depends on the fire method.
I've transferred upplim_destruct_metamorph, maximum_leaf_wetted_fraction, interception_fraction, and Jmaxb1 (now jmaxb1 and pft-dimensioned) from the namelist to the parameter file and run the following test subset with bfb results with ctsm5.3.002 (current base for b4b-dev branch).
SMS_D_Ld5.f10_f10_mg37.I2000Clm45Fates.derecho_intel.clm-FatesCold
SMS_Ld5.f10_f10_mg37.I1850Clm45BgcCrop.derecho_intel.clm-crop
ERI_D_Ld9.f10_f10_mg37.I1850Clm45Bgc.derecho_gnu.clm-default
ERP_P64x2_D_Ld5.f10_f10_mg37.I1850Clm45BgcCrop.derecho_intel.clm-crop
ERP_P64x2_D_Ld5.f10_f10_mg37.IHistClm45BgcCru.derecho_intel.clm-decStart
SMS_Ld5.f10_f10_mg37.I2000Clm50FatesRs.derecho_intel.clm-FatesCold
SMS_Ln9.ne30pg2_ne30pg2_mg17.I2000Clm50BgcCrop.derecho_intel.clm-clm50cam6LndTuningMode
ERI_D_Ld9.f10_f10_mg37.I2000Clm50BgcCru.derecho_intel.clm-default
ERP_D_P64x2_Ld3.f10_f10_mg37.I1850Clm50BgcCrop.derecho_gnu.clm-default
ERP_D_P64x2_Ld3.f10_f10_mg37.I1850Clm50BgcCrop.derecho_intel.clm-default
ERP_D_Ld5.ne30pg3_t232.IHistClm51Sp.derecho_intel.clm-default
ERI_D_Ld9.f10_f10_mg37.I1850Clm60Bgc.derecho_gnu.clm-default
ERP_D_Ld5.f10_f10_mg37.IHistClm60Sp.derecho_intel.clm-default
ERI_D_Ld9.f10_f10_mg37.I1850Clm60Bgc.derecho_gnu.clm-default
ERP_D_Ld9.ne30pg3_t232.I1850Clm60BgcCropG.derecho_intel.clm-clm60cam7LndTuningModeLDust
SMS_D.f10_f10_mg37.I2000Clm60Bgc.derecho_gnu
SMS_D.f10_f10_mg37.I2000Clm60Bgc.derecho_intel

Next, plan is to convert the parameters in #2830 (Jmaxb0, wc2wjb0, r_mort) to pft-dimensioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Projects
None yet
Development

No branches or pull requests

3 participants