-
Notifications
You must be signed in to change notification settings - Fork 27
Namelist options for DMS tuning #704
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
Namelist options for DMS tuning #704
Conversation
jmaerz
left a comment
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.
Fine with the changes - potentially consider my previous comment.
hamocc/mo_param_bgc.F90
Outdated
| real(rp), protected :: dmsp1 = 10._rp ! 2*5. production with temp | ||
| real(rp), protected :: dmsp2 = 0.0011_rp | ||
| real(rp), protected :: dmsp3 = 0.0864_rp ! bacterial removal, but reduced 50% to increase dms emissions | ||
| real(rp), protected :: dmsp3 = 0.1296_rp ! bacterial removal, but reduced 50% to increase dms emissions |
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.
Hi @TomasTorsvik , I am in general fine with the changes, but if time allows: maybe put the original values of Kloster et al. 2006 in the comment lines? Further: I didn't check the values - @JorgSchwinger might wish to have a second look.
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.
Yes, that makes sense. I see that the comment line with "50%" is wrong / needs updating.
hamocc/mo_param_bgc.F90
Outdated
| real(rp), protected :: dmsp3 = 0.1296_rp ! bacterial removal, but reduced 50% to increase dms emissions | ||
| real(rp), protected :: dmsp4 = 1.25_rp*0.10_rp ! production with delcar, but reduced by ~7% | ||
| real(rp), protected :: dmsp5 = 1.25_rp*0.02_rp ! production with delsil, but increased by a factor of ~2 | ||
| real(rp), protected :: dmsp5 = 1.36e-02_rp ! production with delsil |
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.
Is it a good idea to already change the default values?
I would slightly prefer to leave them unchanged for now, do the tuning simulations with namelist and then update the defaults for the final release.
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.
OK, that makes sense. I will revert the changes for default values.
noresm3_0_beta09: Update CTSM, BLOM - CIME: `cime6.1.143_noresm_v1` - ccs_config: `ccs_config_noresm0.0.55` - BLOM: `v1.12.22` - NorESMhub/BLOM#704 - CAM: `noresm3_0_021_cam6_4_121` - NorESMhub/CAM#245 - CICE: `noresm_cice6_6_1_20251129_v1` - CISM: `cismwrap_2_2_007_noresm_v1` - CTSM: `ctsm5.4.002_noresm_v1` - NorESMhub/CTSM#178 - FATES: fates_params_sci.1.88.6_api.42.0.0_14pft_nor_sci1_api1 - MOSART: `mosart1.1.12_noresm_v1` - WW3: `ww3_interface_noresm0.0.18` - CISM: `cismwrap_2_2_007_noresm_v1` - CMEPS: `cmeps1.1.23_noresm_v1` - CDEPS: `cdeps1.0.83_noresm_v2` Testing: - `prealpha_noresm` all PASS (new baseline noresm_develop/noresm3_0_beta09) - `aux_cam_noresm` several expected BASELINE failures and unexpected SUBMIT failures due to unavailability of input data from new NCAR server - `aux_clm_noresm` all PASS (new baseline ctsm_develop/ctsm5.4.002_noresm_v1) - `aux_blom_noresm` all PASS (new baseline blom_develop/noresm3_0_beta09)
Add option for tuning constatns
dmsp3,dmsp4,dmsp5through namelist options. Default values: