closest point to the very first would be removed from the list, so the initial list reduces from 100 to 98. From the 98 i pick one and search the remaining 97 for the closest. From the remaining 96 i pick again one and search in the 95,...
(The product I want to result is:
having a number of random lines in 3D space, produced by an even number of points as discribed, this shall be the initial springs for a ("selfadjusting") tensegrity. Each one of these lines (later springs in kangaroo) get divided in three areas - that means four points. These four points again are the "attractor points" of neighbor springs, so the strut "knows" where to set the next elastic connection,...the rest I´ll have to figure out)
angelos…
me in 19 different pipeline components. Marginally better, but I'll still need to do this operation approx. 80 times...gulp.
Here's a wishlist request for David: expose string inputs in the Geometry Pipeline for Layer and Name. If I had that, I could change one string to swap my whole geometry set! (My layers have names like "B1 red rail", "B1 blue rail" etc., then the next time I'll want "B2 red rail", "B2 blue rail" etc.)
BTW, I'm happy to script something in C# if it will help: maybe I could write something like the Geometry Pipeline that takes a string input for layer name? Hmmm...
…
this target list:
(a1, b1, c1, d1)
(a2, b2, c2, d2)
(a3, b3, c3, d3)
....
What I want to do is injecting one more value (arbitrary angle in my case) to each point before I cull many of them - so that each point brings its angle data along.
Any hep would be greatly appreciated. TIA
…