ESCOMP / ESCOMP/CTSM

Have long compset names that don't match -- fail with a graceful error

Open
#2,794 0 comments 0 reactions 1 assignee Claimed by @ekluzek View on GitHub
usability
Dominant language
Fortran
Stars
352
Forks
361
Avg merge
2d 21h
Merged PRs (30d)
7

Description

This came up in the context of #2561 where a CLM51%NONTHRO long compset failed to do the wrong thing, because NOANTHRO wasn't defined for CLM51.

The real problem is that it doesn't die with a graceful error -- and only does the wrong thing silently. And that's an important problem to fix.

The discussion in #2561 also says this..

> The same kind of problem shows up for DV and VIC for the setting of: CLM_BLDNML_OPTS, and for CLM_USER_MODS for CMIP6 and WACCMCMIP6 and FATES-SP.

For LND_TUNING_MODE invalid settings set an invalid value and hence die with an error. We should do something similar for these.

There's also some restrictions to configuration setup for description at the top that would catch certain issues -- but NOT all of them.

_Originally posted by @ekluzek in https://github.com/ESCOMP/CTSM/issues/2561#issuecomment-2135889570_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.