Grasshopper

algorithmic modeling for Rhino

different output trees @ intersection components

hey there,

can someone explain to me why output trees of CCX, LLX components differ so. please have a look at the files, thy !

Views: 403

Attachments:

Replies to This Discussion

When two curves intersect, they can do so a potentially infinite amount of times. If you intersect a Sine curve with a Cosine curve then you'll keep on getting intersections for as long as you care to make them. Two lines however only ever have a single intersection (or crossing) point. So the CCX component needs to be able to output multiple intersection events for any two curves whereas the LLX component only needs to output one. This is why the output of CCX is more complicated.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

thanks david for your answer,

my question was more about the tree structure of the output.

a simpler example :

why i have to use here shift component, isnt this compareable to the example with the multiplication in the ss ? thank you

No, CCX will intersect two vertical curves with three horizontalones with a potentila of infinite intersections per combination. Hence a tree with two banches(per vert) fanning out to three (per hor) ending in a list (intersections) per path.

Mult will match ten B with ten A each. So you get ten branches (per B) with a list of ten results (per A).

thank you for explenation.

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