b.e30_beta06.B1850C_LTso.ne30_t232_wgx3.168

Open
#96 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
fortran
Domain
hpc

Research direction

Start by comparing this issue with configuration 169 (#95), then inspect SourceMods/src.drv/shr_flux_mod.F90 and the changes referenced in amwg_dev issue #691. Use the linked case and sandbox details to understand the configuration context. Done means configuration 168 applies the specified sea-surface and 2-m temperature averaging for surface saturated humidity in the ocean bulk-flux formulation.

Written by the indexing model from the issue text.

Description

Purpose:
168 = 169 + mods from https://github.com/NCAR/amwg_dev/issues/691
For the purpose of the bulk flux formulation over ocean include both the specification of surface saturated humidity (ssq) surface temperature to be based on an average of the sea surface surface and 2-m temperatures.


Description:

Same configuration as 169 (#95):
except:

SourceMods/src.drv/shr_flux_mod.F90

Case directory:


Sandbox:
Locally (if still available): /glade/work/hannay/cesm_tags/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/hannay/archive/b.e30_beta06.B1850C_LTso.ne30_t232_wgx3.168/
  • CAM Climos: /glade/campaign/cgd/amp/amwg/climo/b.e30_beta06.B1850C_LTso.ne30_t232_wgx3.168

Contacts:
@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.