Lesley De Cruz

Thanks! I haven't used custom timesteps so far, so just to check -I thought it was allowed to have non-integer timesteps if you specify custom ones, so what happens in...

I think this can soon be merged, although it shows that the current way the plugins are structured is hitting its limits. It leads to a lot of duplicate code...

I think the current state is fine, it enables nowcast plugins in pysteps, opening the door for all kinds of data driven methods. The reason why I said it's hitting...

Thanks for this contribution! We discussed how to make it more generic and @joeycasey87 will try to refactor it tomorrow to allow for various kinds of post-processors including new ensemblestats...

Apologies for the force-push, but I have done a rebase to the latest master version. The plan is now to clean up some of the dummy code (maybe move this...

Also, by updating the cookiecutter template I just realised that we broke the standard pysteps tests, so best to merge these changes in quite fast.

This can be done using ray as suggested by @dnerini see example: https://colab.research.google.com/drive/1pMAJZ8AZe7gUDgCogenfdlc-ayX6kVVM?usp=sharing

Lukas-Kanade from openCV provides some uncertainty information about the u,v components, can we use this?

For this, the pysteps/nowcasts/interface.py needs to include a new function to discover the new nowcast methods from plugins - similar to importers currently, and postprocessors (cfr ongoing work on pysteps-precip-type).

To (attempt to) answer your questions: > Would this be a simple extrapolation with linear blending? Possibly, but the question is what the weights would be. One could take the...