generative modeling for Rhino
The Simple answer would be to create a set of all the points and then remove the end points from it using the Set Difference Component.
However a better approach would be to only try and intersect the curves once and thus avoid intersecting them with themselves. This approach is both more efficient with processing but also you can identify which curve intersects with which curve by the resulting data structure.
The methodology is to create a list of the first four curves A,B,C,D
Then create a combination of the last four curves in four lists where each list decreases in length.
therefore you intersect A with B,C,D,E
B with C,D,E (As A and B were intersected above they don't need to be done again.)
C with D,E
D with E
and there is no need for E to be done as it appears in every list above.
Whts the expression you wrote inside C of the series?
and what is it for?
The List Length is 5 but I only want the series to go up to 4 so the expression is as shown in the Yellow tool tip in the image "C-1".
One thing I didn't show in the image is the series actually starts at 1 not 0 by default. (S=1)
The results are you want to shift the curves by 1, 2, 3 and 4 whilst the wrapping flag remains on False therefore shortening the list.
With corrections attached.
The first Shift component needs to be S=-1 to get the First 4 curves A,B,C,D(,E) otherwise you get (A,)B,C,D,E
And the Series component needs to start at 1.
I hope this is clearer.
I feel like i'm back in kindergarden counting intersections...
and about that, you mentioned erlyer that you can figur out throgh the data structure whitch curves are intersecting.
I'm looking into the lists and and icant figure out the structure, i'ts differnet then the oreginal structure (10 items VS 11 items...).
eventually i want to create a list of curves and the number of intersections it has.
is it possible?
don't forget that when curves do not intersect there will be a null result and thus gets placed at the branch level above the other results
I agree with your assessment. I will ask David to look in to it as there would seem to be a bug based on this. I've tried a few different orders of curves and there seems to always be an extra null value even when it produces an intersection. All misses seems to be fine and all hits seem to be fine but when you have a curve with hits and misses there is a null value for every hit.
Here's a file to demonstrate all intersection possibilities.
I Think i'm onto a salution, ill add it up as soon as i get it wokrin'...