Cull Pattern

Hey there,

I want to set a cull pattern that changes according to a different number slider.

So if the number slider changes, the cull pattern should adjust to it automatically.

If the slider is set to the number "10" for instance, the cull pattern is ten times "true" and then one time "false" at the end. So it kicks out the 11th, unneccessary element.

Is there any way to set the cull pattern so that if I change the number slider for instance to "12", that it kicks out the 13th one? Or do I have to change the Booleans all the time manually for those different situations?

Thanks in advance,

Maria

Replies to This Discussion

Permalink Reply by Maria Cervinka on July 17, 2015 at 6:36am

Ok thanks for the info and your work!

I also have a different file, which is more complicated and even more chaotic probably haha, but at least it should be more correct in geometric terms I guess.

If you want you can have a look at it.

And the BPJ you would use only where the tension rope is connected? Or also at the top or bottom for example?

Attachments:

ellipse_090615.gh, 115 KB

Permalink Reply by Maria Cervinka on July 17, 2015 at 6:38am

P.S.:

fyi: this was my first file I did in grasshopper. So sorry for the chaos! The second one is more simple but also schematic and cheating a little bit here and there. It is more like to find the right geometry rather then having exact geometric parameters and control if it's actually working or not..

Permalink Reply by Maria Cervinka on July 15, 2015 at 6:43am

Thanks a lot for your file!

But actually it seems to work if I just use Cull Index (-1) like phillip suggested.

But thank you :)

Permalink Reply by peter fotiadis on July 17, 2015 at 8:37am

Nesting in answers is rather limited, so let's start from "node" 0:

1. Get a reworked thingy + 2 indicative (but ugly) Kangaroo membrane simulation options. Used the K1 (099) engine, mind.

2. Membrane modules in your solution are rather decorative (too small for any shading function worth the name): you need something big. But making that big a stunning design ... that's another animal.

3. Arches definitions ARE not correct (arches vary during the retraction): you need a totally different approach.

4. As I said, I could do it rather easily by replacing all components with a single C# (plus the correct arch design, plus detailed linkages ... plus using blocks in an assembly/component fashion for the arches, BP joins, pivoting joins et all) but it could be 100% useless to you since you don't speak the language.

Moral: long is the path (and hilly)

Attachments:

Maria_beams_WIP_V2.gh, 392 KB

Permalink Reply by Maria Cervinka on July 17, 2015 at 12:39pm

Allright, I'll try.

Thank you so much for your help!

Have a nice weekend,

Maria

Permalink Reply by peter fotiadis on July 19, 2015 at 2:08am

BTW: even if this is Academic ... it's still a mechanism and as such ... requires a totally different approach: FIRST solve the kinematic details and THEN do whatever (including some membrane that DOES provide some shading).

1. Get this from an very old "similar" project. It gives you an indication about how to design the arch folding linkage. Obviously is not modeled in Rhino.

2. Arches SHOULD not been just cold bended tubes: you'll end up violating all the laws of engineering > use trusses instead (see 1).

3. If the required tension to the fabric is due to the "unfolding" event(s) > be prepared to have a very bad shaped membrane: this concept can't apply the required forces for a smooth result (and if it does ... you'll need big members completely ruining the aesthetics).

Attachments: