review of dataflow parametric modelling tools (grasshopper, houdini and generative component)

we are doing a review of the 3 major dataflow parametric modeling tool. we have created an example and re-did it in all 3 modelling program. we will then look at the construct of each network and try to do a review of all the 3 modelling software.

attached is the example we created. Please give ur comments on it , or suggest any other way to reduce the complexity of the network.

( i am not a very experience grasshopper user, so any improvement to the network is welcomed)

thanks

the example schema is base on this few parameters:

1. the tapering of the component is dependent on the distance between the affector and panel

2. the extrusion is base on the direction of which the panel is facing , those facing directly north will have less extrusion then those facing away

3. the material of the panel is base on both the area and the direction of the panel.

*those panel facing north and have big area will have a clear transparent glass , as if to let more light into the space (white colour)

*those panel facing north and have small area will have a normal glass (black colour)

*those panel not facing north and have a big area will have a double glaze glass to keep away heat (red colour)

*those panel not facing north and have a small area will have a normal glass (black colour)

Attachments:

the_worm_pavillion.3dm, 27 KB
the_worm_pavillion.ghx, 1.3 MB

Replies to This Discussion

Permalink Reply by Danny Boyes on December 24, 2010 at 4:32am

Anything recursive would be best handled in a VB.NET or C# Script Component. These can be found on the Math Tab in the Script Section. Or Since the release of v0.8x Clusters have made a long awaited return, although somewhat limited at present. Clusters allow you to select a bunch of components and compact them into their own individual component. This then makes it easier to deploy multiple copies around the canvas. Although it has to be said that it's not working right at the moment.

Permalink Reply by chen kian wee on December 28, 2010 at 12:32am

I have look through the networks uploaded by Danny Boyes and Matt Gaydon, revised my network and clean up alot of the duplicate data , look cleaner now. But for the triangulation of the surface is there a more compact way of doing it ?

Attachments:

the_worm_pavillion(revised).ghx, 922 KB
the_worm_pavillion.3dm, 27 KB

Permalink Reply by Danny Boyes on December 28, 2010 at 2:18pm

I wrote a fairly lengthy post here to explain the errors of your ways, but Ning seem to have lost the text part of my post so to summarize: It comes down to list management and putting your faith into the tree structure to allow GH to handle the same thing over and over. Here I have replicated your pattern for creating the triangles for each face but instead of breaking up the lists of data points I have simply changed the starting point of some list with the aid of the Shift Component, allowing GH to apply this pattern of point selection for all faces on all objects.