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

If input_lakedepth is lost between restarts, CLM Lake model will crash #146

Closed
SamuelTrahanNOAA opened this issue Dec 18, 2023 · 0 comments · Fixed by #139
Closed

If input_lakedepth is lost between restarts, CLM Lake model will crash #146

SamuelTrahanNOAA opened this issue Dec 18, 2023 · 0 comments · Fixed by #139
Labels
bug Something isn't working

Comments

@SamuelTrahanNOAA
Copy link
Collaborator

Description

If CLM Lake is used in FV3 as intended, input_lakedepth should never be 0. The world is not always ideal. Sometimes there may be a change in orography between cycles of a cycled model. Or, something may go wrong in the model restart procedure. This can lead to input_lakedepth=0 on some points.

When that happens, there is a divide by zero in the clm lake mode.

Steps to Reproduce

  1. Fill input_lakedepth with 0 in a restart file.
  2. Restart the model.
  3. Witness the divide by zero error.

Additional Context

This was discovered during RRFS parallels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant