Geodesic sphere - pyramids

Replies to This Discussion

Permalink Reply by peter fotiadis on April 26, 2016 at 10:50am

Well ... I don't have the add-ons used but ...  you may find this attached def interesting.

Using: SandBox for the connectivity trees required (get it prior running the def).

The good news are that works (explanations about the freaky half-lines top tree later on).

The bad news are ... well you know them already don't you? he ,he.

The ugly news are that you'll need a LOT of other stuff (most notably clash detection) in order to design a real-life truss. Activate all the 3 available boolean toggles and see what I mean. Clash detection is performed obviously via trigonometry and NOT via Brep to Brep soild "ops".

BTW: Given the opportunity, in general and in order to avoid using excess material I would strongly recommend to work on triangulated meshes (and/or line graphs). The real-life benefits in cost are pretty colossal. Of course by making negative the "d" you can control the triangulation "orientation" (usually the skin is applied there).

best, Lord of Darkness

Attachments:

• Geodesicdome_Truss_V1.gh, 125 KB

Permalink Reply by Katarzyna Przybyła on April 26, 2016 at 11:28am

hmm, i installed SandBox but nothing happens, GH says:

"Missing object chunk in archive. An object could not be found in the document, it will be missing once the file is loaded."

what's wrong? 

 

 

Permalink Reply by peter fotiadis on April 26, 2016 at 11:43am

Quite probably nothing serious: my Image (I guess). What happens if you accept the MIA thing and load the def? It should work 100% OK (otherwise: Plan Z:  Skype).

Permalink Reply by peter fotiadis on April 26, 2016 at 12:33pm

Added 2 other test cases (WB required).

BTW: the half top strut freaky approach is used because ... well... in real-life we use only instance definitions in similar cases: thus the "tube" part is indifferent whilst the sleeve (not included) the connecting bolt (MERO KK and the likes) and the cone are the things that matter the most.  So for each top pt (node, that is) there's a rather direct tree structure related with the corresponding paraphernalia.

And despite what people believe clash checks concern mostly the connecting bolts (but truth is that they don't penetrate that much as shown here [and they are far more slimmer]).

Attachments:

• Geodesicdome_Truss_V1A.gh, 127 KB

Permalink Reply by Katarzyna Przybyła on April 26, 2016 at 12:35pm

It looks like that: is anything missing? 

Permalink Reply by peter fotiadis on April 26, 2016 at 12:44pm

is anything missing?

Er ... hmm ... a very important thingy ... but anyway it works without that.

WAIT a minute > where's the Sandbox component?

Permalink Reply by Katarzyna Przybyła on April 26, 2016 at 1:34pm

ok, now it works, thank you very much ! <3 <3 

Permalink Reply by peter fotiadis on April 27, 2016 at 2:19am

And since I have a feeling that the top half lines approach MAY be a "bit" confusing for you, here's the V1B.

See the 1M challenge as well > do it and win the usual Fotiadis ACME Industries prize: tons of Da Morgada sardine cans (in pure mineral oil).

Attachments:

• Geodesicdome_Truss_V1B.gh, 128 KB

Permalink Reply by peter fotiadis on April 27, 2016 at 3:22am

Added a "don't bother" clause (try/catch) and now you can also use an open surface (> mesh) for your truss adventurers.

Attachments:

• Geodesicdome_Truss_V1C.gh, 140 KB

Permalink Reply by Katarzyna Przybyła on April 28, 2016 at 12:23pm

WOW, thank you so much !! 

Permalink Reply by peter fotiadis on April 28, 2016 at 1:11pm

Next case: get ANY line graph (good, bad, wrong, right > who cares? not me anyway) and do that:

"that" is a truss where the node "sockets" (the while cylinders) are variable in length because clash detection is  auto performed and their length is accordingly adjusted in order to allow clash free struts (the pink ones). See nodes in the left bottom corner and compare with nodes around the middle of the whole combo. A bit freaky eh?

Note: Not something that could impress these Germans ( MERO Gmbh :Trusses Uber Alles) since this (a bit naive) approach dictates 3d printing on the nodes (not - yet-  recommended for real-life AEC stuff).