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

Including Kd_bkgnd in diag table causes runs to fail #684

Open
knlowman opened this issue Jul 11, 2024 · 0 comments
Open

Including Kd_bkgnd in diag table causes runs to fail #684

knlowman opened this issue Jul 11, 2024 · 0 comments

Comments

@knlowman
Copy link

I'm running a modified version of CM2G that uses MOM6, SIS2, AM2, and LM3. If the Kd_bkgnd diagnostics (both from ocean_model and ocean_model_z) are included in my diag table, the runs always fail about 9 months and 25 days into the run, regardless of the run start date and the value of KD_ADD. The error always resembles:

srun: Terminating StepId=135061639.0+0
srun: Terminating StepId=135061639.0+1
slurmstepd: error: *** STEP 135061639.0+0 ON c5n1551 CANCELLED AT 2024-07-09T12:28:45 ***
srun: Force Terminated StepId=135061639.0+1
forrtl: error (78): process killed (SIGTERM)```
@knlowman knlowman changed the title Including Kd_bkgnd in diag table causes runs to fail Including Kd_bkgnd in diag table causes runs to fail Jul 11, 2024
@knlowman knlowman changed the title Including Kd_bkgnd in diag table causes runs to fail Including Kd_bkgnd in diag table causes runs to fail Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant