algorithmic modeling for Rhino
Tags:
OK, get this and we talk later about other things.
BTW: do you understand fully what connectivity trees are? How they work? Why we use them?
If not ... I could spend a few lines explaining the gist of these mysterious things.
best, The Lord of Darkness
Connectivity and trees are not the same thing although the former is expressed via the latter.
A List is something that samples things (numbers, points, lines, breps, booleans, cats, dogs and probably alligators as well) in "order" (i.e. : this apple is the first and that one is the next).
A Tree is a way to keep Lists "in order". This grid of apples has rows as branches (of Lists) and columns as Lists of apples. The "nesting" (depth) is controlled via the Tree dimension(s) - for instance this: sardines.Add(sardine, new GH_Path(md,sd,td)); puts a(nother) sardine in a List that is accessed within the sardines "collection" (the Tree, that is) via the main dimension (md) then via the second (sd) and then via the third. (td)
A connectivity is something that relates a List of things. What apple is connected with what other? What sardine is cousin to what sardine? This means that the index of a given apple/sardine (within the list of apples/sardines) becomes the branch in the connectivity tree where the indices (per branch) are the indices of items within the list of apples/sardines.
In simple cases connectivity branches they have depth = 1 (like in this case). It could be different if lists/trees of surfaces were used - instead of just one surface.
BTW: A lot of spaghetti around > removed some (and corrected a minor bug).
Use this rather than the V1 (spot the autoZoom).
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by