b.e30_alpha09e_m.B1850C_MTso_Gris_Marbl.ne30_t233_wgx3.389

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
git
Domain
hpc

Research direction

Start by comparing issue #391 and the referenced case directory. Review user_nl_cice, the cesm3_0_alpha09e_MARBL .gitmodules change, and the git-fleximod update step; then run the specified case with r_snw set to 0.5. Done means the case completes and its diagnostics and output are available at the listed locations.

Written by the indexing model from the issue text.

Description

Purpose:
Same as 388

  • r_snw = 0.75->0.5

Description:
Same as 388 (#391) except

  • user_nl_cice
r_snw = 0.5

Case directory:


Sandbox:

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

  • On github:

# get the cesm tag
git clone -b cesm3_0_alpha09e https://github.com/ESCOMP/cesm.git cesm3_0_alpha09e_MARBL

# Make the following change in the [submodule "mom"] section of .gitmodules:
cd cesm3_0_alpha09e_MARBL
emacs -nw .gitmodules
-        fxtag = mi_260625
+        fxtag = mi_260715

# check out the tag
./bin/git-fleximod update

Diagnostics:


Output:

  • Raw output on derecho (if still available): /glade/derecho/scratch/hannay/archive/b.e30_alpha09e_m.B1850C_MTso_Gris_Marbl.ne30_t233_wgx3.389/
  • CAM Climos: /glade/campaign/cgd/amp/amwg/climo/b.e30_alpha09e_m.B1850C_MTso_Gris_Marbl.ne30_t233_wgx3.389

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


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.