run_neon calendar issues in transient case #2471
Assignees
Labels
bug
something is working incorrectly
Comments
slevis-lmwg
added a commit
that referenced
this issue
Apr 15, 2024
B4b neon Description Fixes neon bugs related to calendar issue with transient cases created by run_neon and an odd error that can be fixed by removing redundant information in usermod_dirs. CTSM Issues Fixed: Fixes #2470 Fixes #2471 Fixes #2474 Are answers expected to change (and if so in what way)? No, removes bug in NEON cases Any User Interface Changes (namelist or namelist defaults changes)? only changes to usermod_dirs Testing: OK: ./run_ctsm_py_tests -u OK: ./run_ctsm_py_tests -s PASS: ./run_sys_tests -s clm_pymods -c ctsm5.1.dev176 --skip-generate
Merged
1 task
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brief summary of bug
This is one part of the issues being discussed in #2437. Specifically the error running transient cases related to a basecase that is created with a NO_LEAP calendar and transient clones being set to GREGORIAN. See thread here.
General bug information
CTSM version you are using: [output of
git describe]ctsm5.1.dev175
Does this bug cause significantly incorrect results in the model's science? [Yes / No]
no, but it makes run_neon less easy to run
Configurations affected:
transient cases single point created with run_neon
Details of bug
I know @TeaganKing and @ekluzek are taking a deeper look at #2437, but I think we can address this calendar issue with updates to default shell commands in usermod_dirs
I'll open up PR to b4b-dev to address this issue.
Outstanding issues (that I'm aware of) are
--experimentflag starting in ctsm5.1.dev172 #2433 and@ekluzek and @TeaganKing I'll let you decide how deeply you want to dive into the cime detail outlined here, but I think in the short term the updates to usermods I'll propose will help address this.
The text was updated successfully, but these errors were encountered: