Grasshopper

algorithmic modeling for Rhino

My tensegrity demo works very well in kangaroo before I add this membrane fabric(16 mesh) on top of it, my goal is I want all these mesh following the movement of my tensegrity structure when I'm doing the simulation in kangaroo, can someone help me fix this definition? thank you

Siyu

Views: 3426

Attachments:

Replies to This Discussion

No ... wait a bit please since that @$%$@ translation almost brings the Lord (of SardineLand) into His limits (maybe I'll switch to Tequila ASAP for some spiritual assistance).

Non planar X: due to rigidity requirements ... well ... needs FAR more "struts" than you can imagine (AND OTHER mysterious thingies).

Plan Z-1: FORGET Kangaroo (sorry Daniel): mastermind(?) a way to make that @%$@% X thingy out of a surface: WE DON'T use "relaxed" surfaces for that type of stuff since ... er ... a XTruss is just like any other truss (only hideously more expensive).

Plan Z: what about forgetting all that freaky stuff and marry a rich girl? Think about that.

best, Lord of SardineLand (ex Lord of Darkness).

Hahahahaha, in china we says man should find a right father in law..

yes that's part of my plan, but before that I need to figure out this freaking tensegrity definition thing and get into MIT arch next semester, Then I will spend 2 years there to achieve this goal haha

good night !

You mean that MIT: 77 Massachusetts Ave, Cambridge, MA 02139 ??

If so ... I'll e-mail you soon some stuff (related with instance definitions) to give MIT a "challenge" , he he

BTW: What about Paris? (a bit on the ultra Kitsch side of things, but no pain no gain).

Yes, I'm applying for MIT Architecture computation now which the application is due on 31,Dec

That will be great if you can share some definition with me!! Thanks A lot!!

OK, let's continue form node 0 on that rabbit hole (Plan B: abandon ship, he he) thread of yours:

1. After 32 minutes! (mama mia) a STEP214 is made that is readable by Rhino (the previous attempts were "amusing") - but all the intelligence is lost + the assembly hierarchy is lost + my dog is MIA as well.

2. This relates ONLY with some members of a given XFrame (meaning that you need a zillion things [or some "abstract" ones] for a relatively "large" scale tensegrity truss).

Meaning: instance definitions ... or Armageddon.

Meaning: some "adjustments" in a given definition having in mind similar systems (Plan B: abandon ship).

3. The fact that the 4 (ex single "tube") members are NOT planar (while ones in the previous example) AND their angles are variable as well (blue in the previous example) makes things hideously complex: we need ways to achieve levels of freedom AND some rigidity: the other way is to machine custom MERO type of stuff (balls, that is) that could host the adapters (but this means 1 zillion DIFFERENT balls).  So in this variant shown the angles are managed by a "fixing" ring and rigidity by double tube [MERO type] members. Cables shown are classic Norseman stuff (Plan B: abandon ship).

4. So it's not a mystery why nobody uses that type of nonsense stuff for real-life AEC projects (other than smallish decorative things with a very limited load bearing capacity).

5. All that ... BEFORE the ultra complex system that supports the roof.

STEP mailed but ... well ... what about doing some nice tensile membrane? I have a zillion "simple" defs that do that sort of stuff.

best, Lord of Darkness (ex SardineLand Lord)

BTW:

1. Why people think total nonsense is really deep - The Washington Post

2. Get a surface > buy a zillion Styrofoam cubes > do this, do that > add a double tetra truss > win the 1st price for the most effective way to spend cash for no reason.

 

Wait a Second! you mean the shape of double tetra truss underneath is following the movement of the flag!?

Yes

You never listen eh? (shown your stuff used as a "template": for above/below > just offset the surface, or approximate it via proper roof modules [ that's obviously the proper way to do it]).

1Z Q: WHAT I'm talking with all these replies? In plain English: THE ONLY way to deploy a T thingy on a surface is to create a def that does this AND NOT involve K/K2/Kn by any means.

Of course this is about 5% of the whole (a proper system, clash detection, instance definitions, connectivity trees, holes on surfaces, roofing, cats, dogs and one alligator).

I just realize the whole point you made yesterday..

I didn't thought about to give up kangaroo until I have been told to make this complicated shape...

Well ... I said it MANY times: K has nothing to do with this type of stuff - it could serve IF we are after some tensile membrane ... but attempting a tensile membrane and THEN trying to "lay-out" a flat T on that is kinda a 3rd marriage.

BTW: This surface of yours is very easy (it's the very same thing with a planar rectangle at least with regard the creation logic). Things are a bit hotter if trimming info is around (It's far more complex than you can imagine ... since some T types they can't "exist" as standalone modules).

Did I've mentioned closed surfaces?

Did I've mentioned a capability to individuality modify some nodes in order to host "columns" and the likes?

And here comes the pain: the very same thingy of yours used for a MERO KK system (~10 times cheaper and ~10 times more capable to sustain some proper loads like heavy snow, nuclear blast, seismic stuff, elephants on the roof etc etc). Shown with the Sin distortion option = true meaning that W depth varies from a min "around the boundary" to some max around the "center". Not shown the various paranoid random options (ideal for Vodka fanatics) that yield ... ultra paranoid stuff.

Classic MERO:

So ...who on Earth would opt for a T truss? unless tons of Vodka are used at agreement time.

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service