generative modeling for Rhino
Hi,
Based on Carlos Hernandez's article on parametric design in the Sagrada Familia ("Thinking Parametric Design: introducing parametric Gaudi", Design Studies, Vol 27/3), I wanted to make a Grasshopper model for one type of Gaudi's columns.
Everything works perfectly until the superimposition of the two twisted column-elements. Afterwards, a boolean intersect should be done which should result in the final column. For some strange reason, the boolean intersect fails when keeping the loft options at their default settings. When rebuilding one of the lofted columns, everything seems to work (from time to time).
I've attached a graphical representation of what should be done (from step 1 to step 4), as well as a Ghx (0.8.004). Any help (also with regards to possible optimization of the model) is more than welcome!
Tags: boolean, column, gaudi, intersection, twist
Permalink Reply by Mateusz Zwierzycki on December 13, 2010 at 7:38am Hi,
very interesting issue to solve ;) Booleans are the worst thing to do, so always try to simplify boolean "indegrends". In attachment you can find full working (on my desktop) definition. now the only problem is when rotation is 45 degrees, but i think you shouldn't worry about that.
Permalink Reply by Mateusz Zwierzycki on December 13, 2010 at 7:39am 7 KB less than yours ! ;P
Hi Mateusz,
Now that is a clean and performative solution! I never really thought about doing the intersection on the copied rectangles in Z-direction...
What is the reason for flattening the input of the Loft-command? I mean, it joins the two lists of data (the two curves), but what is its purpose in this case?
Thanks a lot for the time you spent on it :) It is indeed an interesting issue. I'm discussing it in my thesis on algorithmic/parametric design as a contemporary way to solve "classical" mathematical approaches in architecture.
Permalink Reply by Mateusz Zwierzycki on December 13, 2010 at 9:39am no problem,
about flattering data in loft : i don't know how about now (gh 0.800004) but in earlier versions lofting sometimes failed because of different levels of data tree branches... so now i always try to flatten data, just in case of making any problems :]
and now as you can see in this file, if you disable flattering, loft won't work. if you don't want to flatten data, just use "simplify tree" block after intersecting squares.
Permalink Reply by Luis Fraguada on December 13, 2010 at 8:34am Here is a version I did as an example in a class here in BCN. Its based on the drawings found in the various books by Burry on the Sagrada Familia... esp this one:
I used Curve Booleans instead of booleaning the whole thing with solids...the images shown in these books really spell it out super clearly.
Hi Luis!
That book looks awesome. I've put it on my Amazon wishlist straight away (seems to be sold out at the moment).
Your definition is - at this stage - too expanded for the purposes I need it for: explaining parametric design to "beginners" (which includes myself actually) ;)
Permalink Reply by Mateusz Zwierzycki on December 13, 2010 at 10:57am if so, i think the most important (or one of the most important things) in GH is data matching (i mean data trees)... i made a big mistake not understanding first what data tree exacly is. watch these videos to make your mind clear about data ;] its good to understand such things in beginning, just to don't make something over and over again.
http://designreform.net/2009/04/rhino-grasshopper-list-management/
http://designreform.net/2009/04/rhino-grasshopper-data-matching/
Permalink Reply by to] on October 6, 2011 at 7:44am Hi,
this is my try :) without boolean at all
© 2012 Created by Scott Davidson.
Powered by