-
Notifications
You must be signed in to change notification settings - Fork 183
Fix docs from #491 #525
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
Fix docs from #491 #525
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #525 +/- ##
=======================================
Coverage 84.14% 84.14%
=======================================
Files 168 168
Lines 14507 14507
=======================================
Hits 12207 12207
Misses 2300 2300
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I'm getting now a
|
|
Many thanks, @dnerini! And apologies that we overlooked these small issues. Can you check if my minor change fixes the issue? The file is there, so it should be able to find the path. |
|
hey @RubenImhoff thanks for having a look! The error is till there unfortunately: |
I see - do you know if the data from |
|
Does your last commit make the difference, @dnerini? |
|
@RubenImhoff I think I managed to fix it with b72804c, but now the build gets killed during the compilation of the new example because of memory, see https://app.readthedocs.org/projects/pysteps/builds/29712523/ can we try to make this example more lightweight? perhaps we could halve the spatial resolution of the input data? |
|
Hi @dnerini, many thanks for your fixes so far! It indeed remains challenging to run this in the examples due to the high memory needs of the ensemble data from DWD. I have now upscaled the grid resolution of both NWP and radar with a factor two. Let's see if that does the trick. |
|
Unfortunately not, still same issue with memory: https://app.readthedocs.org/projects/pysteps/builds/29715456/ Do you know how much is currently needed to run the same example locally? Could you profile it? |
|
Pity! The DWD data is heavy.. I just profiled it: Current version (upscaled with a factor 2): After upscaling to 4x coarser resolution: So, the upscaling helps a lot, but reading the data (and processing it) is currently the bottleneck.. |
|
Uhm i see, thanks for the profiling! Indeed the build fails even with factor 4... but I wonder, is the data imported with double precision? Maybe you can try to pass |
That seems to have lowered most of the memory needs, but the line |
|
build succeeded! have a look: https://pysteps.readthedocs.io/en/fix-docs-491/ now it would be a good moment to have a close look at the docs about the EnKF blending. @m-rempel would you have time to have a close look too? |
|
Thanks for the additions, @dnerini! This looks great. :) |
|
Thank you @dnerini and @RubenImhoff for your efforts regarding the docs and especially the tutorial. I have to apologize that we missed that part of the documentation issue and also for the immense memory consumption. I have now taken a closer look at the tutorial section and it looks really good to me! Maybe, if one wants to change something, then the description of |
See https://app.readthedocs.org/projects/pysteps/builds/29674718/
docs rendered here: https://pysteps.readthedocs.io/en/fix-docs-491/