b.e30_alpha08o.B1850C_MTt4s.ne30_t232_wgx3.330_branch.fix

Open
#326 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by comparing this run with issue #314 and issue #323, then review the listed namelist and seasalt emissions changes. Use the case directory and CESM sandbox paths to identify the run setup, and consult the diagnostics and output locations after the forcing run completes. Done means the B1850C_MTso spinup run with T4S chemistry has been performed and its outputs are available.

Written by the indexing model from the issue text.

Description

Perform forcings for the B1850C_MTso spinup run


The run is set up identically to https://github.com/NCAR/cesm_dev/issues/314 however includes T4S chemistry

It is the same as #323 with additional changes in the namelist in lbc, and seasalt emissions.

seasalt_emis_scale= 1.55D0

flbc_file = '/glade/u/home/jzhan166/scripts/LBC/clean/LBC_17500116-20221216_CMIP7_0p5degLat_OCSupdate_c250523.nc'
flbc_list = 'CCL4', 'CF2CLBR', 'CF3BR', 'CFC11', 'CFC113', 'CFC12', 'CH3BR', 'CH3CCL3', 'CH3CL', 'CH4', 'CO2', 'H2',
'HCFC22', 'N2O', 'CFC114', 'CFC115', 'HCFC141B', 'HCFC142B', 'CH2BR2', 'CHBR3', 'H2402', 'OCS', 'SF6', 'CFC11eq'


Case directory:


Sandbox:


Diagnostics:


Output:

  • Raw output on derecho (if still available): /glade/derecho/scratch/tilmes/archive/$CASE/
  • CAM Climos: /glade/campaign/cgd/amp/amwg/climo/$CASE
  • Timeseries: /glade/campaign/acom/acom-climate/tilmes/CAM7/$CASE

Contacts:
@cecilehannay


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.