(or rather @piac , I think this is for you )
I have been playing with the Shortest walk component recently and I have noticed a strong performance hit when using custom lenghts.
Please see the screenshots below.
Without custom path lengths the difference between searching one path and searching 100 is negligible.
with custom lengths the difference in time between searching one or hundred paths is
much bigger (although not quite linear).
This leads to calculation times of several hours when applied to 10k points with custom lengths, while the other methods breezes through it in a matter of few minutes…
Many thanks in advance!
gh file attached181011_PerformanceShortestWalk.gh (497.8 KB)