b.e30_alpha08a.B1850C_LTso.ne30_t232_wgx3.283

Open
#252 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
hpc

Research direction

Compare this request with issue #251 and inspect the referenced case directory and its user_nl_clm configuration. Verify the three listed parameter and crop-calendar paths, then check the linked case and diagnostic locations to confirm the requested case setup is complete.

Written by the indexing model from the issue text.

Description

Purpose:
same as 282 with changes to:

  • paramfile
  • stream_fldfilename_cultivar_gdds
  • stream_fldfilename_gdd20_baseline

Description:
Same as 282 (#251) except

  • add to user_nl_clm
paramfile = '/glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/paramdata/clm60_params.ctsm6_li2024.c250822.nc'
stream_fldfilename_cultivar_gdds = '/glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/cropdata/calendars/processed/gdds_20250809_025305.tweaked_latlons.nc'
stream_fldfilename_gdd20_baseline = '/glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/cropdata/calendars/processed/20230714_cropcals_pr2_1deg.actually2deg.1980-2009.from_GDDB20.interpd_halfdeg.tweaked_latlons.nc'

Case directory:


Sandbox:

  • Locally (if still available): /glade/work/hannay/cesm_tags/cesm3_0_alpha08a

Diagnostics:


Output:

  • Raw output on derecho (if still available): /glade/derecho/scratch/hannay/archive/b.e30_alpha08a.B1850C_LTso.ne30_t232_wgx3.283/
  • CAM Climos: /glade/campaign/cgd/amp/amwg/climo/b.e30_alpha08a.B1850C_LTso.ne30_t232_wgx3.283

Contacts:
@cecilehannay @dlawrenncar @slevis-lmwg @wwieder @olyson


Extra details:

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.