-
Notifications
You must be signed in to change notification settings - Fork 167
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
No reproducibility of steps blended nowcast when using noise_stddev_adj='auto' #346
Comments
Hi @mpvginde thanks for reporting this issue! Do you want to go ahead and submit a pr (looks like a simple fix)? Otherwise I'll try to have a look on it |
Sure @dnerini. I'll have a look at it. |
A small update: |
See #337 (comment) Should be fixed with PR #347 |
* Bugfix: fix random placement of ensemble members in numpy array due to dask multi-threading (#337) * Bugfix: make STEPS (blending) nowcast reproducable when the seed argument is given (#346) * Bugfix: make STEPS (blending) nowcast reproducable, independent of number of workers (#346) * Formatting with black --------- Co-authored-by: ned <[email protected]>
When running 2 identical blended nowcasts with
pysteps.blending.steps.forecast
usinga fixed
seed
and setting
noise_stddev_adj = 'auto'
,the results (sometimes) differ.
I suspect this behavior is coming from the
pysteps.noise.utils.compute_noise_stddev_adjs
function.This function takes the
seed
argument, but inside the function theseed
is always set toNone
:pysteps/pysteps/noise/utils.py
Lines 102 to 106 in be8eea4
Leading to different normalization weights for every run and impacting the final results, preventing reproducibility.
Kind regards,
@mpvginde
The text was updated successfully, but these errors were encountered: