Hi brendon, when you say "array" you mean "point" right?
Judging from the screenshot, you're dealing with some fairly complex trees here. For example the [Sec] component outputs 173 curves, stored in 101 branches. The first 5 branches in that tree all contain a single curve, so there must be other branches further down that contain 2 or more curves. I don't know why [Divide] outputs more branches (210) than it receives through the [C] input, that might be a bug. [Sec] will now output nulls if the Plane and the Brep you're intersecting do not result in any curves. These nulls will propagate into the [Divide] component where they will result in yet more nulls in the [P] output. I also don't know why [Clean] has removed all branching data (reducing the tree to a single branch), did you enable the Flatten option on the [D] input for [Clean]? Can you send me this file (+ the required Rhino document) so I can have a detailed look? -- David Rutten [email protected] Robert McNeel & Associates On Mar 20, 11:25 am, brendon_c <[email protected]> wrote: > Hey David, > > im curious if i could get a very brief explination of the how the > paths are determined. > > when i am dividing 173 curves into segments of 500mm. I get 16,096 > arrays, in 210 paths with several null returns. When i flatten and > clean I get 16,052 arrays in one path (ok i understand this part). > > what determines how the string of arrays is divided into seperate > paths ? > > http://grasshopper3d.googlegroups.com/web/path%20logic%202.jpg?gsc=d5... > > thanks so much > > brendon
