ESCOMP / ESCOMP/CISM-wrapper

Have CISM abort with an error when NOEVOLVE is chosen in the compset?

Open
#98 4 comments 0 reactions 1 assignee Claimed by @Katetc View on GitHub
bug
Dominant language
Fortran
Stars
4
Forks
18
PR merge metrics
No merged PRs in 30d

Description

In CTSM we ran into this problem when trying to run with CISM2%NOEVOLVE.

https://github.com/ESCOMP/CTSM/issues/2561

Could this be made into something that is disallowed with an error? I suspect it wouldn't be hard to do. And certainly should be as NOEVOLVE is currently being removed and moved to DGLC in CDEPS. So NOEVOLVE should be marked as deprecated and something that shouldn't be used.

Does that sound like something that the CISM team could do?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.