Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't allow SP, fates, or nofire tests to turn fire_emis on (and make sure our tests don't do this either) #2762

Open
ekluzek opened this issue Sep 16, 2024 · 0 comments
Assignees
Labels
bfb bit-for-bit enhancement new capability or improved behavior of existing capability usability Improve or clarify user-facing options

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Sep 16, 2024

When -fire_emis is added to CLM_BLDNML_OPTS it should fail for configurations where fire-emissions won't be passed back. Right now that's SP mode, when nofire is turned on for BGC, or for FATES.

The FORTRAN code and build-namelist should disallow these options.

And we should make sure our testing don't turn on fire-emissions for these configurations.

Related issue: #2759

@ekluzek ekluzek added enhancement new capability or improved behavior of existing capability bfb bit-for-bit usability Improve or clarify user-facing options labels Sep 16, 2024
@ekluzek ekluzek self-assigned this Sep 16, 2024
@samsrabin samsrabin added this to the cesm3_0_beta04 milestone Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bfb bit-for-bit enhancement new capability or improved behavior of existing capability usability Improve or clarify user-facing options
Projects
Status: In Progress
Development

No branches or pull requests

2 participants