Grasshopper

algorithmic modeling for Rhino

I've just been asked to check some work I did back in August 2009 where I digitised some graphs in Rhino and Grasshopper.

Pre Data Trees*:

Post Data Trees and extra Plug-ins:

* I should Say the version of Grasshopper was capable... I was not

Views: 1029

Replies to This Discussion

15 instructions is a pretty small size for any algorithm. It still often surprises me how many components are sometimes needed to do something simple, and how few to do something complicated...

This is awesome. I still see people building definitions that look a lot like the former... terribly frustrating.

+1 for at least your wires in the former are legible :)

@danny from which plugin does the first component come from?

@david that also astonishes sometimes  

Human it produces a list of layer names from which I can then filter out the ones I want from what they start with hence the qc* and ip* match text driven dispatches. The there is a dynamic pipeline from human that takes an input of layer names. So I end up with 2 sets of 4 graphs each with 8 curves that I then intersect with curves from another layer set at the correct x spacing across the graph. The last component is from ghowl spreadsheet writer.

Nice Danny. Can you post a Hi-Res Image of the pre-data trees variant, so that components are visible.

Will do. But its nothing fancy I think curve line intersect then clean tree then I'm sure sort os one of the next ones then ending on deconstruct point. I'll post in the morning

as promised, but as mentioned, not very exciting.

Very much a copy paste definition.

It was version 0.6.0019 just after trees were introduced.

Thank you.

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