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

check_inputdata

Open
#89 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
backend

Research direction

First determine whether this belongs in MOM_interface, NCAR/MOM6, or ESMCI/cime, then reproduce the izumi case with the missing inputdata files and inspect the case.submit and initialization logs. Done should mean the responsible project and expected behavior for missing files are established, including whether the failure occurs before the run starts.

Written by the indexing model from the issue text.

Description

I'm not sure if this belongs here or in NCAR/MOM6 (or maybe in ESMCI/cime?), but I tried to port my MOM6+MARBL branch to izumi and forgot to copy my inputdata files over -- everything is stashed in /glade/work/mlevy until I finish testing and we decide on a final fileset.

Anyway, I didn't realize I had forgotten to copy these files over, and case.submit didn't complain about this missing files... instead, it started the run and hung during init. Looking at the logs, it crashed when calling MOM_temp_salt_initialize_from_Z() so it didn't even try to read the non-existent files (which leads to a question unrelated to this particular issue, but does CESM+MOM run on izumi yet?).

edit to add: the crash in MOM_temp_salt_initialize_from_Z() comes from a sandbox based on cesm2_3_alpha02d using the intel compiler; when I tried the nag compiler I got build errors (in FMS, I believe)

Dominant language
Jupyter Notebook
Stars
6
Forks
23
Avg merge
1d 4h
Merged PRs (30d)
1

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/MOM_interface

All issues in ESCOMP/MOM_interface

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.