Skip to content

run_neon base case must be of same run type as a requested clone #1926

Description

@wwieder

Brief summary of bug

Creating a default NEON case with ./run_neon generates a base case and a transient simulation. Subsequently running with --run-type ad from that original base case fails. Bug is resolved when the base case is created as the same run type as the cases being cloned from it.

General bug information

CTSM version you are using: latest dev tag ctsm5.1.dev115
Thanks to @TeaganKing for first identifying this bug.

Does this bug cause significantly incorrect results in the model's science?

No, but is potentially confusing and frusterating for users

Configurations affected:

NEON single point cases created with .run_neon script

Details of bug

I created a NEON case with the following command, which creates a base case BART and transient case, BART.transient. This simulation runs fine
./run_neon.py --neon-sites BART --neon-version v2

Subsequently cloning a BART.ad case from that base case, however, fails.
./run_neon.py --neon-sites BART --neon-version v2 --run-type ad --base-case BART

These errors can be avoided by creating the base case as the same run type as subsequent clones. For example the following create and runs a ABBY base case that works fine for cloning other .ad simulations

./run_neon.py --neon-sites ABBY --neon-version v2 --run-type ad
./run_neon.py --neon-sites MOAB --neon-version v2 --run-type ad --base-case ABBY

Important output or errors that show the problem

The cesm.log error states

ERROR: (shr_stream_findBounds) ERROR: rDateIn lt rDatelvd limit true

The atm.log error states

(shr_strdata_get_stream_pointer_1d)  strm_ptr is allocated for stream field strm_Faxa_precn
 (shr_stream_findBounds) ERROR: limit on and rDateIn lt rDatelvd
   180101.000000000        20180101.0000000

Definition of done.

Activity

  1. added
    documentationadditions or edits to user-facing documentation or its infrastructure
    bugsomething is working incorrectly
    on Dec 13, 2022
  2. added this to the milestone on Dec 13, 2022
  3. added
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    on Dec 15, 2022
  4. removed
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    on Jan 26, 2023
  5. removed this from the milestone on Apr 25, 2024
  6. added theissue type on Mar 28, 2025
  7. added
    docs:?Type of documentation issue unknown
    docs-loc:?Location of needed change(s) is unknown
    on May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugsomething is working incorrectlydocs-loc:?Location of needed change(s) is unknowndocs:?Type of documentation issue unknowndocumentationadditions or edits to user-facing documentation or its infrastructure

    Type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions