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 phillip on July 15, 2015 at 4:48am

Why not use [Cull Index]?

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

Thanks, it works!

Didn't think that the solution would be so simple,

Thank you :)

Permalink Reply by peter fotiadis on July 15, 2015 at 5:57am

Like this?

Attachments:

Cull_this_cull_that.gh, 11 KB

Permalink Reply by peter fotiadis on July 15, 2015 at 6:39am

Also:

Attachments:

Cull_this_cull_that_V2.gh, 20 KB

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

Thank you very much for your solution. It also works fine, exactly as I need it!

But I have another problem with my file.. You seem to have pretty nice skills, maybe you can have a look at it?

I have extruded the curves in my file but they are still intersecting eachother.

How can I manage that the beams are not intersecting but just "touching eachother".

I would like to have that one beam is underneath and the other above the other one and not going through it. In the lowest and middle intersecting points it should be like that (on top of eachother) and at the highest point they should lie next to eachother.

Can you help me out?

Attachments:

2015.07.15.gh, 21 KB

Permalink Reply by peter fotiadis on July 15, 2015 at 7:18am

Yikes ! a lot of spaghetti there, he he

That's very easy with code (but I guess that I should make it with GH components: my "lucky" day).

Other than that: in real life "touching each other" is entirely out of question (even with "oval area" welding [never mind about what this means]: VERY bad engineering approach). So ... a connection MUST be around: therefor I'll add some realistic stuff (a "flange", a ball joint [hideous], a plate [less is more], a cat, a dog or whatever suits best the occasion: an alligator, what else?).

Permalink Reply by Maria Cervinka on July 15, 2015 at 7:42am

Haha, spaghetti. Nice.

Yeah, makes sense, totally agree with you.

Thanks a lot for your time and effort, I'm already so excited about your solution!

Permalink Reply by peter fotiadis on July 15, 2015 at 8:09am

Hmm ... after inspecting the chaotic chaos (Mama Mia) > you need a classic ball pivot join (BPJ) for these folding arches: this means at least a clearance of 20-30 cm depending on size/maker (and cash). BTW: Hinges are hideously kitsch - especially big ones. Sineblock type of joins last a week (or two).

PS: membranes are impossible to make that way, or to put it differently: you "waste" tension forces for no reason: the more flat a membrane is the more you pay for nothing. Even if this is Academic ... well ... it's good to be in the Path, he he (which is long and hilly).

PS: Did I mention the bottom straight tube? No, No (and No).

So, let's make space for the BPJ stuff (by recomputing the "slave" arches) and we talk later about the whole membrane thingy.

more soon

Permalink Reply by peter fotiadis on July 15, 2015 at 10:19am

Get a preview (but WHAT a chaos: I barely resist to remove them all and do it the proper way: via the Dark Side, he he) on that ball-pivot join(s) matter:

Arches "on-top" are the masters and the others ... presumably the slaves. A "line" connects the ball pivot join ends (represented by a stupid enlarged tube for demo purposes). 3 joins per master arch (costing slightly less than the GNP of Nigeria - SS316L stuff all around for more than obvious reasons).

2 versions of BPJ = the top (at Arc.MidPoint) is the main (the bigger) and the left/right are the smaller ones.

Next: Er ... hmm ... clear the chaos and do some proper membrane thingy: should I use Kangaroo? - I'm thinking the pros and cons (hope that Daniel doesn't read this, he he).

Attachments:

Master_and_slave_arches_Maria_V1.wmv, 2.7 MB

Permalink Reply by Maria Cervinka on July 15, 2015 at 10:31am

Nice! Thank you. The joints look like they make sense, haha.

But to be honest I have no idea how those ball pivot joints or kangaroo work exactly..

The file generally is very schematic. I improved the membrane situation. The tension rope is curved now. I also started to split up the arches into "theoretical" ones (the basic ones that cross eachother) and "actual" ones, that are not intersecting.

Maybe you can have a look? But probably it's still too chaotic for you, haha.

Who is Daniel btw? ;)

Attachments:

2015.07.15.gh, 25 KB

Permalink Reply by peter fotiadis on July 15, 2015 at 11:46am

OK, get a demo ... about why IT DOESN'T work (this is not the way to define folding arches: spot the length that varies when "folding" these things).

A total rewrite is required (including the membrane concept) ... but if I do it (very easy) I'll use C# and it could be useless to you.

PS: Daniel == Kangaroo (a very smart fella I must say).

Moral: another walk into the rabbit hole, that one

Attachments: