Grasshopper

algorithmic modeling for Rhino

I want to make this form with grasshopper, can someone give me some logic?

In the attachment is a tensegrity rhino model, I want to re-make it by grasshopper, but I didn't find a good logic yet, can someone help me take a look?

 Thank you

Siyu

Views: 2648

Attachments:

Replies to This Discussion

Hmm ...

I have a variety of defs that do tensegrity trusses using a variety of "modes" (including yours) but unfortunately all use C# and not a single native component.

BTW: your case is also doable with components as well.

So here's the deal: If no good Samaritan can provide a native components solution AND you think that a code based one could be helpful to you, I could post something for you. 

Hello Peter,

Thank you for your reply,

This is something i have been looking for an entire semester but never find it..

I know the things you made probably super complicated but I really wanna know more about it and learn from you, would you mind share more information with me?

Also in the attach is the GH file i got and the photo of my physical model, I trying to use linear actuator replace some cables, then control the entire shape by control the length of actuator, however, whenever I change the length in the slide, my compression units are changing too..

do you have any idea why my components doesn't work?

again thank you so much for helping me.

Siyu

Attachments:

Sorry I forgot the rhino

Attachments:

I'll look on it but working with components is not my forte.

I mean that I prefer dealing with data structures "directly" (via code) so to speak - but THIS is a matter of personal preference unless things are heading towards the next step: using instance definitions (see attached image), individually controlling items in collections, recording variants and other ultra mysterious/ominous thingies , he he.

In fact any tensegrity logic is not complicated at all ... but the code part is (especially when adding "real-objects" like the "nodes" captured in your screen shot - either imported "blocks" or geometry defined inside GH, "stored" as a block and then placed as such).

For instance: GH can place things like these with respect a given Topology in case that you have real-life tensegrity trusses in mind (Note: not applicable for this particular case of yours - without some mods in the assembly).

 

BTW: The Kangaroo "test" attached above can answer (up to a point) to puzzles the likes: is my combo "capable" or it would collapse?

more soon, best, Peter

 

BTW: Speaking solely about Topology matters; are you after flat solutions or your dream is:

1. Use surfaces as the "underlying template" for the T truss (see my firstly attached  images - the ones with the white/blue struts - where any closed/open surface can serve as a "guide"). If yes are these Breps (trimmed stuff)? Are these sampled into Lists?

NOTE: obviously using surfaces dictates the adoption of a variable node system like the one captured above (but this is for heavy AEC real-life T trusses) capable to "adapt" VS a range of "angles".

2. Use some magic way that allow you to alter nodes on an individual basis and some another that allows you to record the history of your "results".

3. Use some global policy (say attractors, random stuff or better: some math equation) that can vary the nodes

Sorry it took me a little long to understand the component you made for me (way better than mine!)

"2. Use some magic way that allow you to alter nodes on an individual basis and some another that allows you to record the history of your "results"."--I don't know if I understand correctly,  but I do want to alter the length of some cables and record the different shapes of my 'roof'

I'm trying to do some similar things like this project(the link from AA)

http://adaptiveskins.com/computational-development/

"NOTE: obviously using surfaces dictates the adoption of a variable node system like the one captured above (but this is for heavy AEC real-life T trusses) capable to "adapt" VS a range of "angles"." what do you mean about using surfaces? is there any example i can look at?

Thank you

Siyu

Well ... this def makes some abstract struts ... IT DOESN'T make the T truss.

Other than that:

Using surfaces:  I mean these images attached: (In plain English: instead of working with a "flat" grid of points and make the T thingy out of them... divide any open/closed surface/brep (== holes + trimmed boundary) and play ball with these points instead). Obviously further controlling the "nodes" (with any imaginable way is easily doable: for instance random this, random that and the likes).

Variable node system: This means that having in mind your limitations you FIRST design a "system" that can fulfill your goals AND THEN you place components of that into the 3d space (as nested instance definitions) using plane to plane (kinda like the orient component) transformations. Either we must Skype ... or forget it (only doable via code). Affects solely real-life cases and requires some decent feature driven MCAD (I use CATIA and Siemens NX for these). It's not nuclear science but requires a vast experience in order to achieve some optimum system having in mind the hideous cost of bespoke SS 316 L (corrosion) parts.For the cable tensioners use top quality stuff the likes of Norsman

Variants et all: This means an ability to store some "ideas" (i.e. results, so to speak) of yours during your assault VS T trusses. It has to do with volatile and persistent data and other ominous things. Either we must Skype ... or forget it (only doable via code).

In general ... well ... GH can do things that you barely can imagine (good news) but most of them require code.

BTW: King of cable matters:

https://www.google.gr/url?sa=t&rct=j&q=&esrc=s&sour...

BTW: A MERO KK systeme used on some truss (normal or tensegrity). By used I mean that each thing that you see (an accurate representation of real things commercially available) is an instance definition - that way you can have a Rhino file with 10K of these that requires less than 1M (the other option is ... er ... 500 MB).

hello Peter,

I made a new version based on the file you sent to me last night. I got some curve shapes finally, but in a very fake way. I have some new questions want to ask you if you don't mind.

1. in the attachment image, I was going to create some new "pink balls" in the center of the compression units like you did for me on the end of the cables, but I don't know how to select these intersection points, could you give me some thoughts?

2. in the attachment file, you can see when I'm changing the length of actuators, the other cables are more like a fixed cables, they are not following the movement of actuator cables(i want them to extend at mean time), do you know is there anyway I can achieve that?

would you mind share some samples of the work you showed to me?(the one above) it looks super cool i think it will inspire me more, I plan to start learn some basic coding next week.

May i have your email? thank you so much for all your help

i know i'm so bothering.

Siyu

Attachments:

Well ... (alias T for tensegrity)

1. Send me a friendship (!) request in order to provide my e-mail and then ... use it for further discussing all these things.

2. Balls (even pink ones) ARE NOT the way to make some real-life proper nodes for that kind of T truss (we use machined balls solely for MERO KK type of normal trusses).

3. I'll post here soon a modular demo system suitable for this case (real-life for AEC purposes - NOT for decorative/artistic stuff, I don't care about that since I'm an engineer). This would include a policy for the X struts that require a variable linkage (the X angle). and in the same time a multi cable tensioner "bracket".

4. "Basic" coding next week for T trusses ? Er ... well ... are you kidding me right? I mean that ... hmm ...  

5. C# things (about 2+K) around me are classified into 2 "groups": things that are weapons in the right hands and others that serve as demos/start points for mostly abstract cases. The former are internal the latter for public use. I'll remove some sensitive lines from a T truss C# maker and I'll post it here as a "guideline" ... for ...hmm... 4.

All in all:

Provided that you have system(s) on hand (see 3) that work 100% OK in an ideal world you'll need:

A. Something that does the general topology AND (especially) clash detection. Maybe Kangaroo as well as a "first pass" with regard rigidity of the structure in case that you don't adopt a classic T "configuration" (there are many > Google tensegrity).

B. Connectivity trees that relate nodes/edges and maybe faces (say for roofing panels/curtain walls etc etc). Without them is impossible to assemble the T thingy.

C: Something that places real-life "parts" as instance definitions and/or (optional) a "tracking variants history" ability.

D. A bullet proof way to EXPORT things (on an assembly/component schema, say: STEP214 - see C) into a proper BIM app (the likes of AECOSim/Revit) and/or into a MCAD app (the likes of CATIA/NX).

E. FEA/FIM in order to validate the structural ability of the components and the T truss itself.

F. Roofing/cladding/envelope components.

G. "Interactive" cost estimation(s) - T trusses are hideously expensive at least versus "classic" trusses (exactly like a planar glazing system that retails 3++ times more than a humble semi-structural one)

Anyway ... get this (native components for making some "solid" struts) that could be useful (up to a point) for tensegrity adventures: Kangaroo in action (i.e. is it structural capable?)

Attachments:

I start a new node 0 on this thread for clarity.

Took me 2 minutes to locate some "suitable" T system for your case and ... 22 to translate it to Rhino (obviously these things are made far and away from Rhino). Using feature driven solid modeling (AECOSim + NX),  ordinary tube struts, MERO type of hidden joins, Norseman cable tensioneers (commercially available) and bespoke custom parts (tube conical adapters, rotating tensioner brackets, X join and other mysterious paraphernalia). Obviously is fully parametric ... but not the way that you think.

NOT suitable for decorative/artistic stuff: this is designed for large scale AEC Projects.

File format: STEP214

And the real thing (AECOSim + Generative Components) in action:

This approach "deals" with clash situations rather successfully (within reasonable limits). Small torsional forces on the connecting main bolts are present (strut/cables axis don't meet 100%) but it's really not a concern.

Use the 3dPDF as well.

Attachments:

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