PLEASE REVIEW: new coupled run with mods from F cases and starting from the end of 147

Open
#77 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
hpc

Research direction

Start by reading the ChangeLog between alpha06b and alpha06e, then compare the configuration in issue 675 with the end state of run 147 (#69). Review the listed CAM and CLM namelist paths and the proposed year-97 or year-101 hybrid start; done means the relevant working groups have reviewed the configuration and identified no showstoppers.

Written by the indexing model from the issue text.

Description

Purpose of the run

new coupled run:

  • incorporating several modifications we've been testing in F cases.
  • starting from the end of 147.
Description of the run

We are going to start a new coupled run:

  • incorporating several modifications we've been testing in F cases. We aim to match the configuration used in: https://github.com/NCAR/amwg_dev/issues/675
  • starting from the end of 147 (#69) which includes reset_snow and reset_snow_glc north of 45°N and between 100°W and 0°. This state is spun-up and does not experience freezing.

- Namelists modifications

  • CAM: new tuning parameters for dcs and dp1 amd new topo.
bnd_topo = '/glade/campaign/cgd/amp/pel/topo/cesm3/ne30pg3_gmted2010_modis_bedmachine_nc3000_Laplace0050_noleak_20250409_28kmGRISrough.nc'
micro_mg_dcs= 600.D-6
cldfrc_dp1 =  0.05
  • CLM: new land parameters and initial conditions (with the aim of bringing back boreal forests).
paramfile = '/glade/campaign/cesm/development/amwg/inputdata_extra/ctsm5.3.012.Nfix_params.v13.c250221_upplim250.nc'

finidat = '/glade/derecho/scratch/slevis/archive/ctsm53026_BNF_hist/rest/1998-01-01-00000/ctsm53026_BNF_hist.clm2.r.1998-01-01-00000.nc'

- Tag
The new coupled run will use alpha06e instead of alpha06b in order to up-to-date code for cam.
I reviewed the CAM-related changes in the ChangeLog between alpha06b and alpha06e with Peter, and everything looks good from the CAM perspective.
Could other WGs also review the ChangeLog as well to ensure there are no show stopper to using alpha06e instead of alpha06b
https://raw.githubusercontent.com/ESCOMP/CESM/refs/heads/cesm3.0-alphabranch/ChangeLog


- Initial conditions

Start an hybrid from b.e30_alpha06b.B1850C_LTso.ne30_t232_wgx3.147 at year 97 (or at year 101)

Please review: @cecilehannay @dlawrenncar @adamrher @PeterHjortLauritzen @JulioTBacmeister @swrneale @slevis-lmwg @wwieder @olyson @gustavo-marques @fobryan3 @klindsay28 @dabail10 @duvivier @tilmes @billsacks

Suffix in the casename

Suffix

Namelist modifications

Namelist

Source modifications

SourceMods

Sandbox

Requested sandbox or tag

Contact info

Please review: @cecilehannay @dlawrenncar @adamrher @PeterHjortLauritzen @JulioTBacmeister @slevis-lmwg @wwieder @olyson @gustavo-marques @fobryan3 @klindsay28 @dabail10 @duvivier @tilmes @billsacks

Any other relevant information

Enter relevant info

Dominant language
No language data
Stars
11
Forks
3
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NCAR/cesm_dev

All issues in NCAR/cesm_dev

Similar issues

More HPC issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.