You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came up on the forums recently (https://community.naturalcapitalproject.org/t/questions-about-running-delineatelt/2577/1). You can see from the screenshots that on very large DEMs, we're getting an integer overflow when tracking the total number of pixels that should be able to be resolved with a higher-memory counter int, maybe even an unsigned int.
We should take a look at all of the progress logging in routing.pyx to see if there are any other functions where this should be updated as well.
The text was updated successfully, but these errors were encountered:
phargogh
changed the title
Pitfilling and D8 flow direction has buggy progress logging in large rasters
Pitfilling and D8 flow direction progress logging displays integer overflow on large rasters
Mar 15, 2022
This came up on the forums recently (https://community.naturalcapitalproject.org/t/questions-about-running-delineatelt/2577/1). You can see from the screenshots that on very large DEMs, we're getting an integer overflow when tracking the total number of pixels that should be able to be resolved with a higher-memory counter int, maybe even an unsigned int.
We should take a look at all of the progress logging in
routing.pyx
to see if there are any other functions where this should be updated as well.The text was updated successfully, but these errors were encountered: