‘ Grasshopper (Explicit History) ’ category archive
I have been quite fascinated by the recent development of Galapagos for Grasshopper. This is a simple example of its application set up to solve for a 10-point voronoi division within a user-defined boundary where all the parts are divided as equally as possible in terms of their areas. I ran this with an initial population of a hundred for 200 generations. The results are not 100% perfect, but very close (which is the nature of an evolutionary solver I believe).
It’s been a while I’ve played with Grasshopper. It is getting to be more and more powerful. I think I will be exploring more in this world of Grasshopper + VB.NET and also IronPython included in the upcoming Rhino 5. This definition is super simple. It arrays / deforms a component that you define according to the two surfaces and their UV divisions.
In order to use the definition, first define a box, and some geometries within the box as your base component. Then, simply create two surfaces as references for organizing your components. Finally, control U/V divisions.
Ah so, the new version of the Explicit History plug-in for Rhino is out. http://grasshopper.rhino3d.com. It’s going to be a cool new toy to play with :)
This is another way of creating space frames using U/V divisions from two surfaces. Almost the same thing as the previous post. Very simple.
I was looking at the youtube video of this surface blend uploaded by David Rutten: http://youtube.com/watch?v
The updated version of the rhino explicit history has a new feature called “slider” which makes this quite easy. Take a look at these files:
These are the rhino files that perform the explicit history example shown below:
First open the rhino file, and then open the explicit history definition from the ExplicitHistory plug-in interface. Edit the surfaces included the rhino file, and you’ll see how Rhino can actually be parametric. Also note the angle parameter in the “Rot” node and the linear relationship described in the “F(x)” node.
A new plug-in for Rhino4 is being developed. Rhino is finally going (pseudo) parametric. It’s still at an early stage, but the potential it has is amazing. I’ve been exploring this new world of Rhino past few days. It’s like scripting without coding. Here’s an example of what it can do.