A Geodetic exoskeleton tower

by peter fotiadis

Dec 1, 2011

Well friends,

This is my very first attempt in Grasshopper.

In fact I'm doing the very same thing in Generative Components ... because Microstation is a far better AEC platform (VS Rhino) when the parametric exploitation is over. On the other hand Rhino is far superior with regard NURBS capabilities/tools and Grasshopper is 10 times faster (due to a mysterious reason Generative Components becomes ...er... slower from build to build to the extend to be rather "stationary", so to speak - he he).

Back in this naif example: Code is rather garrulous and/or stupid (to say the least) and worst : lass than 2% of the work is finished (smart stuff is like 3rd marriage: triumph of hope VS experience).

See some observations of mine as well (use Saved Views).

I'll be back with a far more realistic approach on the tower theme (and a far better looking solution).

All the best, Peter

 

 

Load Previous Replies
  • up

    peter fotiadis

    See this as well

    1

    Dec 3, 2011

    • up

      peter fotiadis

      Well Jon,

      I have good news, bad news and ugly news:

      1. The good ones are the obvious.

      But the whole "decomposer" thing must brake free from IFC slavery - I can Imagine 1Z (Zillion) things related with AEC stuff that are quite difficult (and meaningless) being classified the IFC way (so to speak) not to mention that their "classes" are on-a-per-case (in most of cases). We need a Canvas inside the Canvas for visually re-arranging trees (i.e mixing bananas with banana splits). I'll be back on that critical  matter soon - with examples

      2. The bad news:

      This is MicroSomething pushed to the limits (for MicroSomething standards, he he):

      PS: In fact you need SLI/CrossFire stuff (and NVidia FX Quadros 4/5xxx to effectively design similar things up to a decent level of detail, that is- a task perfectly OK for NX, forget BIM > in order to finish the race you must finish it first).

      3. The ugly news (no 3dm export around only STEP, but as I said earlier...well, can I have the next question please? he he):

      Yes...no structures/nesting/nothing > meaning a useless collection of scrambled eggs...er..I mean things > a rabbit hole of colossal proportions > zero > adios amigos.

      Moral: the path to glory is long (and hilly)

      Best, Peter

      Dec 3, 2011

      • up

        peter fotiadis

        More ugly news:

        I'm sure that you know the notorious HARNESS thing (based on the work of the GREAT Christoffer Alexander - http://www.patternlanguage.com/leveltwo/ca.htm).

        Well, I did my stuff on that matter (get a set of spatial relations > adjacency matrices > cluster analysis > ... > double espressos (a lot) > spatial arrangements of things > ... > triple espressos > ...). Code is in my beloved Unix O/S (on a H/P internal product: the good old ME30).

        This is one result with regard a WIP hospital "grid" (no fancy non-rectilinear geometry, mind, he he) where the nodes are vertical prefab units, the connecting trusses are the floor support system, the prefab patient rooms may (or may not) being present etc etc etc. Other than the obvious HVAC/people vertical "weaving" ... this is an endlessly expanding thing - because especially hospitals are already obsolete the day that they start operating (tech advances etc etc). 

        In a good day (so to speak) you can solve this mess by addressing questions of type: make an arrangement where the sum of all human movements is the minimum possible (but what about the cats? that's the 1M question).

        This thing could be interesting for you for testing IFC classification matters - what belongs to what (and why) - but only if that MicroNothing could STEP export an iota to Rhino. Doing this with GH (and not get lost in a sea of {0;0;0;0;0;0;0....;1} er...hmm...what about a visual tree manager on a multiple Canvas (and sub Canvas) thing? i.e. Pick a populated "dot" > get the list of stuff in a sub-canvas (and a way better preview of points) > pick another dot > get the list in another sub-canvas  > ah! these are the things that I'm after > combine them > connect them > weave them > whatever >  ... > possibilities are endless

        Notice that the tree on that thing should adapt according the discipline in question: for instance and with regard the Structural perspective what could be the ideal hierarchy of things? Based on what schema? And if there is such a thing ... is it compatible with the Architectural (i.e. space utilization) perspective? What if I need to further expand the tree on selected branches? How deep this expansion should go before calling Samuel Cray?

        Best, Peter

         

        4

        Dec 4, 2011

        Load Previous Replies