b.e30_alpha07c_cesm.B1850C_LTso.ne30_t232_wgx3.239

Open
#199 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
hpc

Research direction

Compare this run with clone issue 193 and inspect the referenced env_mach_pes.xml from run 221. Start with the case directory and sandbox paths, then review the listed diagnostics and output locations to determine the impact of zmconv_num_cin = 2. Done means the experiment has been run and its results are available for assessment.

Written by the indexing model from the issue text.

Description

Purpose:

Test impact of zmconv_num_cin = 2.


Description:

Clone of 234 https://github.com/NCAR/cesm_dev/issues/193, but with increased zmconv_num_cin = 2.

Contains more processors than 234, with env_mach_pes.xml copied over from run 221 https://github.com/NCAR/cesm_dev/issues/177.


Case directory:


Sandbox:

  • Locally (if still available): /glade/work/gmarques/cesm.sandboxes/cesm3_0_alpha07c_cesm3

Diagnostics:


Output:

  • Raw output on derecho (if still available): /glade/derecho/scratch/aherring/archive/b.e30_alpha07c_cesm.B1850C_LTso.ne30_t232_wgx3.239
  • CAM Climos: /glade/campaign/cgd/amp/amwg/climo/$CASE

Contacts:
@adamrher


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.