Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

b.e30_alpha10c.B1850C_MTso.ne30_t233_wgx3.400

Open Beginner friendly
#406 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
fortran
Domain
hpc

Research direction

Start with SourceMods/src.ww3/wav_import_export.F90 in the b.e30_alpha10c.B1850C_MTso.ne30_t233_wgx3.400 case and compare the related fix in issue 398. Run or inspect the CESM-coupled WW3 case and confirm its behavior matches .397, including the affected imported fields.

Written by the indexing model from the issue text.

Description

Purpose:
Adding bugfix for ww model

the CESM-coupled branch imports Sa_u/Sa_v (lowest model level, what CAM exports) instead of Sa_u10m/Sa_v10m; field-list registration, import mask and SetGlobalInput use the same two parameters. This restores the behavior of WW3 from .397.


Description:

Same as 398 but using tag alpha10c except

  • SourceMods

src.ww3/wav_import_export.F90


Case directory:


Sandbox:


Diagnostics:


Output:

  • Raw output on derecho (if still available): /glade/derecho/scratch/$USER/archive/b.e30_alpha10c.B1850C_MTso.ne30_t233_wgx3.400/
  • CAM Climos: /glade/campaign/cgd/amp/amwg/climo/b.e30_alpha10c.B1850C_MTso.ne30_t233_wgx3.400

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


Extra details:

Dominant language
No language data
Stars
12
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.