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

Forecast boundary condition: threshold ice concentration for anomaly persistence #64

Merged
merged 3 commits into from
Mar 20, 2024

Conversation

sanAkel
Copy link
Collaborator

@sanAkel sanAkel commented Feb 27, 2024

This PR provides a patch to previous PR for following case:
of creation of boundary conditions (SST and sea ice concentration; atmosphere-only configuration) using persistence of initial anomaly.

As found by @rtodling, the anomaly persistence can create sea ice concentrations that are > 1 or < 0 which are unphysical and not allowed by the GEOS data sea ice component in default settings.

Proposed patch avoids such instances and also adjusts SST when we know how to do that, therefore ice concentrations and SST have (some) consistency.

@sanAkel sanAkel added the 0 diff The changes in this pull request have verified to be zero-diff with the target branch. label Feb 27, 2024
@sanAkel sanAkel self-assigned this Feb 27, 2024
@sanAkel sanAkel changed the title Threshold ice concentration so that it is >=0 and <= 1. Threshold ice concentration so that it is bounded within [0, 1]. Feb 27, 2024
@sanAkel sanAkel changed the title Threshold ice concentration so that it is bounded within [0, 1]. Forecast boundary condition: threshold ice concentration for anomaly persistence Feb 27, 2024
@sanAkel sanAkel requested a review from mathomp4 February 27, 2024 05:00
@rtodling
Copy link
Contributor

Santha, this seems fine, but to make sure I am running over the data you re-created w/ these fixes. I will let you know.

@sanAkel
Copy link
Collaborator Author

sanAkel commented Feb 27, 2024

Santha, this seems fine, but to make sure I am running over the data you re-created w/ these fixes. I will let you know.

@rtodling, Yes please let me know if those (new files) cause any errors. 🙏

@rtodling
Copy link
Contributor

two runs have completed successfully! I'd say the code changes work fine.

@sanAkel sanAkel marked this pull request as ready for review February 28, 2024 00:11
@sanAkel sanAkel requested review from a team as code owners February 28, 2024 00:11
@sdrabenh sdrabenh merged commit cdafa08 into main Mar 20, 2024
13 checks passed
@sdrabenh sdrabenh deleted the sanAkel/feature/threshold_fraci branch March 20, 2024 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 diff The changes in this pull request have verified to be zero-diff with the target branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants