Grasshopper

algorithmic modeling for Rhino

Updated data and list management components

http://www.grasshopper3d.com/group/milkbox/forum/topics/tree-sloth

Views: 874

Comment

You need to be a member of Grasshopper to add comments!

Comment by David Stasiuk on October 26, 2015 at 10:06am

The most up-to-date tools can be downloaded here: http://www.bespokegeometry.com/2015/07/07/treesloth/

Comment by Khaterah Hadi on October 26, 2015 at 10:02am

Where do I download Tree Sloth from?

Comment by David Stasiuk on June 2, 2014 at 3:17am

Thanks, Arthur! I made all these tools for my own use over the course of a couple of years (mostly for detailing projects) and then figured that some other people might also find them useful. At some point I hope to get around to making some tutorials for how and where I think they're most useful. Do you think that you or your students might be interested in any in particular at some point? I'd love to hear some ideas :) Some of them I'm surprised aren't native (list compare, divide branches, filter unmatched paths, trim ends)...and I also don't get why "flip matrix" requires a data structure only one unique index deep. But I think we all have lots of criticism of data trees in general, and mostly because they are so essential to developing and managing complex definitions.

I haven't encountered the term "tree" anywhere else but here, and I also don't remember seeing any explicit discussions as to why they have been so named, but my guess is that it has to do with the visual programming environment, and that understanding nested lists in a visual manner lends them a "tree" like appearance. I think what's great about them is that they operate like arrays or lists, but are really incredibly dynamic (you can collapse or expand them at any path index level). Ultimately (and in my own personal opinion), because they do operate differently in this capacity to arrays or lists, I think it's appropriate that they are named/conceptualised as soemthing distinct...but "nested collection" would be as good a descriptor as any.

The most comprehensive, up to date description of their behaviours I've seen is David discussion from last autumn: http://www.grasshopper3d.com/forum/topics/datatree-selection-rules

Comment by Arthur Mamou-Mani on June 2, 2014 at 1:30am

Very helpful tools David! Is there a text/discussion on why David chose to introduce trees as opposed to describing it as "nested collections"? Are trees used in any other language?

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service