fix: change extrapolation values for resampling outside radar domain to zero #419
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.
Fix for issue #416.
The small fix introduced here, which sets all extrapolation component values to zero outside the radar domain (instead of to the NWP value as in the code now), gives the following results for the case indicated in #390:
Radar observations (up to 60 minutes ahead):
Blended forecast for ensemble member 0, without the smoothing mask as introduced in #379:
Blended forecast for ensemble member 0, with the smoothing mask:
See also #390 for the previous results. The first lead time is still not perfect, but we got a lot closer already. What do you think?