Use arctan2 for calculating pert_motion_field as opposed to arctan#2
Open
KristianHMoller wants to merge 2 commits into
Open
Use arctan2 for calculating pert_motion_field as opposed to arctan#2KristianHMoller wants to merge 2 commits into
KristianHMoller wants to merge 2 commits into
Conversation
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

We noted, that even with the
alphaandbetanoise parameters both set to zero, runningprobabilistic_advectionin ensemble mode yielded results different from those obtained in deterministic mode. The difference was not constant and for some weather scenarios, almost no difference was observed, while for others the difference was large. Specifically, in ensemble mode, "artifacts" would appear in the nowcast.The source of the discrepancy was tracked to the calculation of
pert_motion_fieldin the scriptModels/ProbabilisticAdvection.py. The original code:np.arctandoes not consider the signs of the input values and additionally, forx=0this will yield issues with division by zero. https://numpy.org/doc/stable/reference/generated/numpy.arctan.htmlBy replacing
np.arctanwithnp.arctan2, these issues seem to be solved. https://numpy.org/doc/stable/reference/generated/numpy.arctan2.html