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

snow depth initialization error and remove unneaded code from ccpp and add protection for roughness length over ice #460

Closed
SMoorthi-emc opened this issue Jan 5, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@SMoorthi-emc
Copy link
Contributor

SMoorthi-emc commented Jan 5, 2022

Description

Provide a clear and concise description of what the bug is.
Also give a description of how to fix the bug.
Snow is initialized incorrectly for the case when land and water coexist (i.e. fractional grid) when the input contains only grid mean snow.

Also, there is some code in ccpp-physics that is not needed anymore and may add error if not removed (specifically for the uncoupled case).

To Reproduce:

What compilers/machines are you seeing this with?
Give explicit steps to reproduce the behavior.

  1. do this
  2. then that
  3. then, oops, look at the bug

Additional context

Add any other context about the problem here.
Directly reference any issues or PRs in this or other repositories that this is related to, and describe how they are related. Example:

  • needs to be fixed also in noaa-emc/nems/issues/<issue_number>
  • needed for noaa-emc/fv3atm/pull/<pr_number>

Output

Screenshots
If applicable, drag and drop screenshots to help explain your problem.

output logs
If applicable, include relevant output logs.
Either drag and drop the entire log file here (if a long log) or

paste the code here (if a short section of log)

Testing:

  1. Have you tested the code changes? On what platforms?

  2. Have you run regression test in ufs-weather-model or ufs-s2s-model with code changes?

  • Will the baseline results change?
  • If the baseline results change, is it expected? Please give brief explanation.

Dependent PRs:

Directly reference any issues or PRs in this or other repositories that this is related to, and describe how they are related. Example:

fv3atm pr: #461

@junwang-noaa
Copy link
Collaborator

The code was merged, the issue is closed.

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

No branches or pull requests

2 participants