E3SM-Project / E3SM-Project/scream

Should we use the same initial conditions for CIME and standalone tests?

Open
#1,885 7 comments 1 reaction 1 assignee Claimed by @bartgol View on GitHub
Atmosphere Driver priority:wishlist
Dominant language
No language data
Stars
79
Forks
54
PR merge metrics
No merged PRs in 30d

Description

This came up in updating some initialization of greenhouse gas variables, and the need to change some initial condition files. Right now, we are maintaining two sets of IC files: one set for CIME runs (what we'd use in a REAL simulation, meaning all components), and one set for standalone tests (what we'd use for running just a subset of components at a time). But, ideally maybe we'd like to be able to use the same IC files that we would use for the full config in our individual tests, so we do not have to maintain two sets of ICs every time you make a change to something, and so that the tests are operating on the same format of file we would use in a full run. For example, our initial conditions for full simulations do not include `p_int`, because `p_int` is initialized by dynamics, but for standalone tests that do not use dynamics we need to include `p_int` in the initial condition files since dynamics are not run.

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.