fellesverkstedet/Bark-beetle-parametric-toolpaths

Postprocessor slower due to non-active components & clusters

Closed this issue · 1 comments

Components and clusters which are not in use inside bark beetle components tend to slow down calculation.

In the last commit I improved this by checking inside the component if a specific function or cluster will be used and if not send "null" as input to the clusters. This has only been implemented in the postprocessor for the drilling operation but I'll update the other ones soon as well.

See below for comparison of speeds:

190814 Before max
190814 After max

190814 Before max 2
190814 After max 2