Skip to content

Conversation

@slevis-lmwg
Copy link
Contributor

@slevis-lmwg slevis-lmwg commented Feb 11, 2026

Description of changes

Copied from this post:

  • New default paramfile for clm6
    paramfile = '/glade/work/linnia/CLM6-PPE/ctsm6_cal/paramfiles/ctsm60_params.c260204.nc'
  • New defaults for CAM7_CLM6 land tuning mode
defo_fire_precip_thresh_bet = 1.4d00
rh_hgh = 80.0d00

Specific notes

Contributors other than yourself, if any:
@wwieder

CTSM Issues Fixed (include github issue #):
Fixes #3725

Are answers expected to change (and if so in what way)?
Yes, due to new namelist defaults

Does this create a need to change or add documentation? Did you do so?
Likely

Testing performed, if any:
I confirmed that I got the correct defaults by submitting (without building and running) two tests:

SMS_D.f10_f10_mg37.I2000Clm60BgcCrop.derecho_gnu.clm-crop
SMS.ne30pg3_t232.I2000Clm60BgcCrop.derecho_intel.clm-clm60cam7LndTuningMode

@slevis-lmwg slevis-lmwg self-assigned this Feb 11, 2026
@slevis-lmwg slevis-lmwg added the non-bfb Changes answers (incl. adding tests) label Feb 11, 2026
@github-project-automation github-project-automation bot moved this to Ready to start (or start again) in CTSM: Upcoming tags Feb 11, 2026
@slevis-lmwg slevis-lmwg moved this from Ready to start (or start again) to In progress - master in CTSM: Upcoming tags Feb 11, 2026
Comment on lines +468 to +469
<defo_fire_precip_thresh_bet fire_method="li2024crujra" >3.0d00</defo_fire_precip_thresh_bet>
<defo_fire_precip_thresh_bet fire_method="li2024crujra" lnd_tuning_mode="clm6_0_cam7.0">1.4d00</defo_fire_precip_thresh_bet>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wwieder the lnd_tuning_mode changes should make sense, but I need to explain line 468:
In our namelist_defaults I found two settings for defo_fire_precip_thresh_bet for fire_method="li2024crujra", one in line 468 (value 1.8) and another in line 338 (value 3.0). I kept the latter value (3.0) but in this location (line 468).

I don't know if the presence of two values should worry us. I confirmed again that the model was using 3.0, so I'm staying with this value as we discussed.

@slevis-lmwg slevis-lmwg moved this from Todo to In Progress in LMWG: Sprint Planning Board Feb 11, 2026
@slevis-lmwg slevis-lmwg changed the title Update namelist defaults: paramfile, rh_hgh, defo_fire_precip_thresh_bet Update namelist defaults: paramfile, rh_hgh, defo_fire_precip_thresh_bet, initial conditions Feb 11, 2026
@slevis-lmwg slevis-lmwg added the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Feb 11, 2026
@slevis-lmwg slevis-lmwg changed the title Update namelist defaults: paramfile, rh_hgh, defo_fire_precip_thresh_bet, initial conditions ctsm5.4.0xx: Update namelist defaults: paramfile, rh_hgh, defo_fire_precip_thresh_bet, initial conditions Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

next this should get some attention in the next week or two. Normally each Thursday SE meeting. non-bfb Changes answers (incl. adding tests)

Projects

Status: In progress - master
Status: In Progress

Development

Successfully merging this pull request may close these issues.

Higher burned area in coupled simulations

1 participant