b.e30_beta06.B1850C_LTso.ne30_t232_wgx3.179

Open
#119 13 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
Stale
Domain
hpc

Research direction

Start by comparing this case with #109, then inspect the listed case directory, its input.nml, and SourceMods in the CESM sandbox. Review the linked diagnostics and available output to assess the changed stochastic GM+E coefficients. The issue does not define a code change or completion criterion.

Written by the indexing model from the issue text.

Description

Purpose:
Tune the stochastic GM+E closure to reduce ocean warming.


Description:

Same configuration as 178 (#109), but with SKEB_GM_COEFF = 0.5 and MEKE_GM_COEFF = 0.5.

MAXTRUNC = 2000
DO_SKEB = True
SKEB_NPASS = 8
SKEB_USE_GM = True
SKEB_GM_COEF = 0.5
MEKE_GMCOEFF = 0.5
SKEB_USE_FRICT = False
SKEB_FRICT_COEF = 0.0

Also, copied input.nml from CaseDocs to SourceMods, and then set:

&nam_stochy
    new_lscale = .true.
    OCNSKEB = 1.0
    OCNSKEB_LSCALE = 300e3
    OCNSKEB_TAU = 21600
    ISEED_OCNSKEB = 20
/

Case directory:


Sandbox:
Locally (if still available): /glade/work/gmarques/cesm.sandboxes/cesm3_0_beta06

On github: https://github.com/ESCOMP/cesm/tree/cesm3_0_beta06


Diagnostics:


Output:

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

Contacts:
@iangrooms @cecilehannay @dlawrenncar @adamrher @PeterHjortLauritzen @JulioTBacmeister @swrneale @slevis-lmwg @wwieder @olyson @gustavo-marques @fobryan3 @klindsay28 @dabail10 @duvivier @tilmes @mbramberger


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.