ESCOMP / ESCOMP/CTSM

Restart read should confirm that each variable's subgrid level matches expectations

Open
#1,710 0 comments 0 reactions 0 assignees View on GitHub
b4b enhancement good first issue
Dominant language
Fortran
Stars
352
Forks
361
Avg merge
6d 6h
Merged PRs (30d)
8

Description

According to #1708 , I believe that @wwieder was able to restart the model using an initial conditions file where the SOIL10_VALUE variable's subgrid level differed between the restart file and the model. The model should abort in this situation with a meaningful error message, via an appropriate error check in either ncdio_pio or restUtilMod.

See also related issue #1709 .

Contributor guide

Open the contributing guide

Research direction

Start by reviewing restart handling in ncdio_pio and restUtilMod, including how each variable's subgrid level is read and compared. Use the SOIL10_VALUE scenario from #1708 as a reference. Done means the model aborts with a meaningful error when any restart variable's subgrid level differs from expectations.

Written by the indexing model from the issue text.

Assessment

Tech stack
fortran
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.