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

Replace remaining POP grids with MOM grids

Open
#1,735 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
data

Research direction

Read the linked discussion in #1569 first to understand which grid replacements are approved: the issue says mg37 and mt12 remain, and recommends mtg17 → mt233 wherever that option exists. Identify the affected grid configurations and update the remaining POP grids to their correlated MOM grids; confirm the regression test answers still pass.

Written by the indexing model from the issue text.

Description

after CESM3_0 enhancement
What is the feature/what would you like to discuss?

Two POP grids remain until they have a correlated MOM grid:

  • mg37
  • mt12

Last update from Mike on this: (#1569 )

At the MOM6 dev meeting, general consensus was that there are changes coming to the 2° mask after the CESM 3.0 release so it probably isn't worth taking the time to use the mt201 mask anywhere -- stick with mg37 and we'll let you know when v2 of the 2° grid exists because at that point you should look into moving the coarser grids to that resolution. For this issue, stick with moving from mtg17 -> mt233 for all grids where that is an option.

Is there anyone in particular you want to be part of this conversation?

No response

Will this change (regression test) answers?

Yes

Will you be implementing this enhancement yourself?

Any CAM SE can do this

Dominant language
No language data
Stars
93
Forks
186
Avg merge
4d 21h
Merged PRs (30d)
18

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 ESCOMP/CAM

All issues in ESCOMP/CAM

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.