Non-symmetric replication of module

Hi all,

This would be a difficult task and I am not expecting anyone to be able to fully solve this issue. However, I would be very grateful if anyone could solve / teach me how to apply my module to this non-symmetrical floor plan.

Basically, this is the module that I have created.

My next task is to replicate it to fit the floor plan of the following.

This is the basic thinking behind the connection of the module.

Once again, this is a complex issue and I am not requesting for anyone to solve it but if someone could provide a path for me to find my way. I will be genuinely grateful.

Thank you!

plan.3dm (703.8 KB) Module.gh (19.0 KB)

If I am understanding you correctly, your module is a section of a tensile roof, with two posts. So in that case you will want your ‘module’ to be a radial section of your total circle, i.e., a ‘slice of pie’. So, you can take your module and morph it onto a unit section of the circle. not a complicated problem, you can use “morph”, “flow”, “taper”
an alternative approach would be to select the compression members, map them to your radial structure, then calculate the tensile ones by point to point.
Of course you will want to eliminate duplicate compression members so you can do this by removing them from one side of your unit module

Thank you for your reply markz. Appreciate your feedback.

Yes, what you written is accurate.
Can I ask if the first method can be done without grasshopper?

Secondly, how would you map them to the radial structure?

Sorry I am still very new to grasshopper.

Thank you!

Well … get the attached as an indicative start point: your issue is 50% related with handling DataTrees and 50% with dealing with Instance Definitions. The latter has to do with real-life, AEC BIM stuff (and code) … so forget it completely for the moment.

367_RingMembrane_JustAHint.gh (13.8 KB)

If you haven’t got the gist of DataTrees I would suggest to take a big break and study these things. Failing to do it … your GH adventures would be full of pain and tears. I guess that tensile membrane modules are in the pipeline … so study Kangaroo K2 as well.

BTW: this is a very easy case via code but that’s not your game I guess.

Thank you.

Yes I agree. I have much more to learn.

Thank you for giving me a direction on where I shall head towards.

I will study it!

:slight_smile:

A few tips more:

  1. If this is a stadium/arena shading thingy … the lateral stability is related with the sum of the “horizontal”/radial beams/members … meaning that your X reinforcements are not required. Kinda a stone in a dome.
  2. If you have tensile membranes in mind the golden rule is one anchor up the next down. If not you’ll need BIG forces to stabilize the modules meaning BIG beams and BIG this and that. Kinda martial arts: finesse is the name of the game.
  3. Avoid 100% vertical columns: they are aestetically clumsy. Kinda the elephant legs syndrome.
  4. Drainage is an issue as well.
  5. Learn some coding language (I do hope the right one).

After finishing with cables and the meshes PRIOR Kangaroo … post here the def and we’ll see various ways to approximate reality (of some sort).

2 Likes

Thank you again for your detail-ed explanation.
Yes this is somewhat a stadium with canvas for shelter. You’re on point with that.
I’ll have to take time to study this whole thing all together again. Right now I am kind of rushing to meet a deadline.
Being a newbie, i’m not sure I can meet your standard :sweat_smile:
But I will try to post the def if I am able to create one.
I really appreciate your effort and passion in trying to solve this issue.

Good day :slight_smile:

Well … you can’t … but exactly because of that … you know what to do:

  1. Never/ever give up.
  2. Try harder and harder and harder until some day … blah, blah.

1 Like

Er … I have at least 50 C#'s that do similar stuff (up to nuts and bolts) so in fact I’m not trying to solve anything. But … even a rough outline of the proper way(s) to adress that one via components is the hard part (doing things via code is 100 times easier).

So … some hints more:

  1. Seat rows N is bigger towards the min axis meaning that the typical stadium layout is like this:



  1. Thus is the layout that dictates the shading structure and not the opposite (form follows function etc etc).

  2. I can provide an entry level C# (a black box for you) as a guideline of doing things: it could include free standing columns, trusses for the sides of the membrane modules (with the one anchor up the other down rule) and the cables required to stabilize the whole structure.

  3. “Roofs” like these have an accessibilty ring (or more) near the inner lips (for servicing lights, sound related hardware etc etc). If that ring has some load bearing capabilities … then a totally different structural approach MAY be the best solution (that way gains some momentum these days).

Added a few lines more on that “indicative”/quideline C#: This is a rational roof abstract layout (but the one anchor up the other down per membrane module rule requires - obviously - beam trusses [shown as curves for clarity]). Lot’s of other secondary cables not shown nor the inner stability ring (that would be suspended from the column tips).

Update: time to give-up: is very hard to do that kind of stuff with components … but this is what I would - in general - suggest for the occasion: