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

FATES doesn't work in branch runs #2903

Open
samsrabin opened this issue Dec 6, 2024 · 0 comments
Open

FATES doesn't work in branch runs #2903

samsrabin opened this issue Dec 6, 2024 · 0 comments
Labels
bug something is working incorrectly FATES API update Changes to the FATES version that also REQUIRE an API change in CTSM FATES A change needed for FATES that doesn't require a FATES API update.

Comments

@samsrabin
Copy link
Collaborator

General bug information

CTSM version you are using: CTSM tag ctsm5.3.009, FATES tag sci.1.78.3_api.36.1.0

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

Configurations affected: Unknown

Details of bug

This is a parallel issue of NGEET/fates#1271. Labeling with both FATES tags because I don't know what it will eventually require to fix.

Important details of your setup / configuration so we can reproduce the bug

It can be reproduced using the test ERI_Ld60.f45_f45_mg37.I2000Clm50FatesCruRsGs.derecho_intel.clm-Fates, which is the ERI version of an ERS test we already run as part of the fates suite.

Important output or errors that show the problem

forrtl: severe (151): allocatable array is already allocated
Image              PC                Routine            Line        Source
cesm.exe           0000000000983A08  edinitmod_mp_init         144  EDInitMod.F90
cesm.exe           00000000006403F4  clmfatesinterface        2089  clmfates_interfaceMod.F90
cesm.exe           00000000006063A6  clm_initializemod         757  clm_initializeMod.F90
cesm.exe           00000000005A8EA3  lnd_comp_nuopc_mp         658  lnd_comp_nuopc.F90
@samsrabin samsrabin added bug something is working incorrectly FATES API update Changes to the FATES version that also REQUIRE an API change in CTSM FATES A change needed for FATES that doesn't require a FATES API update. labels Dec 6, 2024
@samsrabin samsrabin added this to the ctsm6.0.0 (code freeze) milestone Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something is working incorrectly FATES API update Changes to the FATES version that also REQUIRE an API change in CTSM FATES A change needed for FATES that doesn't require a FATES API update.
Projects
None yet
Development

No branches or pull requests

1 participant