Grasshopper

algorithmic modeling for Rhino

How to make a defintion more dynamic (intersectting curves ) ?

Greetings , 

I have build up this definition from a tutorial about curves intersections , it has tow stages :

1-The first stage is about removing intersections at end point of the curves (through culling similar path indexes ) , then removing those from the main list through tree branch.

2-The tutorial stopped at this point where we end up where we had duplicated points of the intersections so I went on and tried to solve an algorithm to remove duplicated points .

My question is :

-Is there a way to fix the definition in order to make it more dynamic incase I had more than three intersecting curves , without the need to manually change it ?

Thanks alot . :)

Views: 885

Attachments:

Replies to This Discussion

Hi.

If you just try to harvest intersecting points without duplication, then there is a dedicated component named "Multiful Curves".(MCX)

Intersect-->Physical-->Multiful Curves

Yes , but I guess the guy in the tutorial avoided using this component because he wanted to have each curve intersection points be on a separate list .

But thanks for the reply 

Intersection points in individual lists will have duplicate points anyway.

you can use MCX. and get it into managable lists just like this....

Just expanding on that a little.... if you want to take it to the end, you just cross-reference the path indices to do the union intersection (as strict).

The final branch path numbers differ to your original file (because the ordering of the cross reference is less manual.) but it is producing the same lists from the input curves I have tested it with.

Attachments:

It would be worth relabeling the path indices too so that they are a little more helpful....

Attachments:

the nice thing about re-labelling the indices is that you can instantly find out which two curves do not touch at all instantly, since it will have a list length of 0.

Nice . Thanks Julian .

I guess the mistake in my solution is I was not able to keep three separate lists .

Yet,one thing I did not understand is the clustered element "Cheery Picker" . I guess it is intended to show the curve when we select its index number from the number slider . 

But the login within the cluster I did not understand ,if you could please explain it to me I would appreciate it ?

The components inside the cherry picker cluster really just cycles through numbers for a given range. (A bit like wrap indices). I should have added an |absolute| in their as well to catch negative values on the slider...(The select Path component doesn't like it when a path isn't present so all the cherry picker cluster is doing is making the '0 To nLines' indices wrap around regardless of the value on the input slider you have. that means it can be plugged in to both the List and the tree path component and demonstrate the two are coherent.

This would have done the same thing. (Slightly better)

Attachments:

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service