b.e30_beta04.BLT1850.ne30_t232_wgx3.121_1pctco2

Open
#37 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
hpc

Research direction

Start by reviewing issue #34, then inspect the cesm3_0_beta04 sandbox and the listed CESM case directory. Apply the specified hybrid-run, CAM, and MOM settings, and use the linked diagnostics and permanent output paths to verify that the 1 percent CO2 experiment completed and its results were saved.

Written by the indexing model from the issue text.

Description

Purpose:

1 percent co2 to assess TCR in 121 configuration


Description:

Same as #34 except:

  • Start from b.e30_beta04.BLTHIST.ne30_t232_wgx3.121 at yr 125
./xmlchange RUN_REFCASE=b.e30_beta04.BLT1850.ne30_t232_wgx3.121
./xmlchange RUN_REFDATE=0125-01-01
./xmlchange  RUN_TYPE=hybrid
./xmlchange  GET_REFCASE=true
./xmlchange  RUN_REFDIR=cesm2_init
  • 4xco2 flbc in user_nl_cam
 flbc_cycle_yr          = -1
 flbc_file              = '/glade/campaign/cesm/cesmdata/cseg/inputdata/atm/waccm/lb/LBC_CMIP6_1pctCO2ramp_y1-165_0p5degLat_c180930.nc'
 flbc_type              = 'SERIAL'
  • turn off CHECK_BAD_SURFACE_VALS in user_nl_mom
    This prevents crashes.
CHECK_BAD_SURFACE_VALS = FALSE

Case directory:


Sandbox:


Diagnostics:


Output:

  • Raw output on derecho (if still available): /glade/derecho/scratch/hannay/archive/b.e30_beta04.BLT1850.ne30_t232_wgx3.121_1pctco2/
  • A permanent copy was saved:
    /glade/campaign/cesm/development/cross-wg/cesm3_development/b.e30_beta04.BLT1850.ne30_t232_wgx3.121_1pctco2
  • CAM Climos: /glade/campaign/cgd/amp/amwg/climo/b.e30_beta04.BLT1850.ne30_t232_wgx3.121_1pctco2

Contacts:
@cecilehannay @islasimpson @dlawrenncar @adamrher @PeterHjortLauritzen @JulioTBacmeister @wwieder @gustavo-marques


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.