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
I think the problem we have in our current automated processing using the FlowAccumulationFullWorkflow tool is related to a large DEM input (20527x9187 Pixel) and limited memory available on a docker host (Processing runs within a Python container).
Our observation: The FlowAccumulationFullWorkflow step exists gracefully after line 631 (Whitebox Version 2.3.1)
I wonder if there were changes made to Whitebox improving this situation. I also think it would be good to not fail gracefully in Whitebox to give a t least some feedback to the user why the tool exists before finishing.
I would be especially interested what solutions others found to address the problem with too large DEM inputs.
I also wonder if using a chunked approach works with this tool as it does both, flow direction and accumulation at the same moment.
In case our issue is really the lack of memory, then maybe a best approach (like chunking) could be directly integrated into Whitebox?
Thanks for looking into this!
The text was updated successfully, but these errors were encountered:
Hi,
I think the problem we have in our current automated processing using the FlowAccumulationFullWorkflow tool is related to a large DEM input (20527x9187 Pixel) and limited memory available on a docker host (Processing runs within a Python container).
Our observation: The FlowAccumulationFullWorkflow step exists gracefully after line 631 (Whitebox Version 2.3.1)
whitebox-tools/whitebox-tools-app/src/tools/hydro_analysis/flow_accum_full_workflow.rs
Line 613 in 59d3451
Input to that tool is the
I found the following threads already touching the same topic of large DEMs
I wonder if there were changes made to Whitebox improving this situation. I also think it would be good to not fail gracefully in Whitebox to give a t least some feedback to the user why the tool exists before finishing.
I would be especially interested what solutions others found to address the problem with too large DEM inputs.
I also wonder if using a chunked approach works with this tool as it does both, flow direction and accumulation at the same moment.
In case our issue is really the lack of memory, then maybe a best approach (like chunking) could be directly integrated into Whitebox?
Thanks for looking into this!
The text was updated successfully, but these errors were encountered: