Random Perforated panels

Hey guys,

I was experimenting on perforated panel facade and have achieved the result

below where i manage to create holes in a double curve srf. However, I find it

a little too rectilinear in terms of the placement of the various size hex due to

having it within the grid. Is there any way that i could make a more random

placement of the hex but still having the attractor points to control the placements?

Maybe not by square grids references.

Cheers

Kelvin Karel

Attachments:

GH_exp 10.3dm, 62 KB
GH_exp 10.gh, 9 KB

Replies to This Discussion

Permalink Reply by Stephen Maher on October 21, 2014 at 9:55am

Have you tried using the [RandomReduce] and [Jitter] components to randomly remove the number of "perforations" in the list you're creating? You can use the [Division] component in junction with these, using the current list length as the dividend. This won't move the holes, rather remove certain items in that list randomly. (You have some control, of course.)

If you're creating the holes based on the centroid of a subdivided surface's faces, this might be an easier option for you. I suppose you can follow the same logic using the intersections of the surface's isocurves as centers simultaneously. That might give you more of the "random" look you're going for.

Hope this helps.

Cheers,

/SPM

Permalink Reply by Kelvin Karel on October 22, 2014 at 12:50pm

Hey Stephen,
It does work. Thanks alot!! However, if i do randomreduce in my main project file i have this overlapping of hex pattern.

Do you know how to remove them?

And... just for my knowledge on grasshopper how do u propose in intersecting the isocurves ?

even so.. Really grateful for your help

Cheers,

Kelvin Karel

Permalink Reply by Stephen Maher on October 22, 2014 at 4:42pm

Without seeing your definition, my best guess is that the "overlapping" is really two surfaces with different perforations on top of each other. In other words, one of your earlier components (a non-final geometry component) is previewed.

See below for an answer to the isocurve question.

All I did was replace your [Area] component with the [Curve|Curve] component. I then connected the P output to where you previously had the Centroid output.

I think this what you were looking for.

Cheers,

/SPM

Permalink Reply by Kelvin Karel on October 23, 2014 at 12:27am

Yea.. i always thought it was one of those srf not turned off but it isn't the case.

I'm not too sure what's the problem. Yep.. and, might be a stupid question, isocurves component evaluate crvs, just like how debrep does to breps? and ccx just gets the point of intersections.

Thx for all the help goodman

Permalink Reply by Stephen Maher on October 24, 2014 at 8:48pm

Hm. Check your final output. The script may be inadvertently creating more surfaces than anticipated or desired. Maybe post your script (or at least an image of it)? I might be able to find the source of the issue if I can dig around your modified definition. Thanks.

The [Isocurve] component doesn't evaluate curves, but "constructs" the geometry's isocurves. Isocurves are embedded within NURBS surface geometry. This component just reveals them (thus allowing you to modify them).

[Curve|Curve] "solves" the intersection of two curves (or two lists of curves). In this case, the inputs are the lists of U-direction and V-direction curves. The outputs are points and parameters as integers or floats.

/SPM

RSS