CCX (Curve-Curve intersection) screws tree

Grasshopper
1

It should be obvious from this example that CCX (Curve-Curve intersection) screws up my trees :

CCX%20tree%20goes%20bananas
CCX%20tree%20goes%20bananas1081Ă—729 98.2 KB

CCX banana tree.gh (197.4 KB)

It finds curve intersections in a branch with no curves, or to be more preccise, it fills an empty branch and screws up the subsequent data scructure, as exemplified here :

CCX%20tree%20goes%20bananas-Consequence
CCX%20tree%20goes%20bananas-Consequence990Ă—666 59.1 KB

2

I had the same problem recently. Turning parallel computing off on the component fixes it.

CCX
CCX1207Ă—827 81.8 KB

2 Likes
3

Hi Sharon,

Thanks for this info.
@DavidRutten : bug !
:slight_smile:

1 Like
4

It is even the case that, with the “Parallel computing” option toggled on, the component takes longer to process the curve intersections…

5

I have found the same problem, and it took me a while to figure out that it was a parallel processing problem. I couldn’t figure out the logic behind the tree that I get with parallel computing.

Regarding the time of computation, you should only be using parallel computation if you are doing a large number of curve intersections. Otherwise it will take longer than linear processing. If you are proficient with trees and sorting your data into branches you can significantly reduce the need for all against all comparisons.