Gradient and randomised reduction of windows from top to bottom

[pennymag]

Hello!

I’m having struggles trying to design solar shading on a building. The idea is for the upper windows to have more solar shades (having more sun exposure), and the lower windows to have fewer solar shades (being more shadowed by surrounding buildings). I want this change to be gradient and also randomised. This is my script so far (being a GH novice and having used google, youtube and chatgpt):

The image shows the result of Cull Pattern. Something doesn’t seem to be working in the Graph Mapper or Cull Pattern component? I can’t figure out what is wrong!

Any advice to keep me moving forward with my design project would be greatly appreciated! Thank you in advance and for taking the time to read my post!

Helpmeplease.gh (7.9 KB)
Helpmeplease.3dm (5.1 MB)

[inno]

I think you can simplify the definition into something like this:

Helpmeplease_Re.gh (24.8 KB)

this is my reference-guide post for these kind of problems

Gradient of points between two curves

It occurs to me that adding a Graph Mapper can magnify the effect of distance from the boundary: [gradient_points_2020Apr6a] gradient_points_2020Apr6a.gh (13.6 KB)

[pennymag]

Thank you so much for the help! That looks great!

[Joseph_Oster]

@inno

this is my reference-guide post for these kind of problems

Heh, heh, that looks familiar. As I said at the time:

@Joseph_Oster

I didn’t really think this through and am not quite sure why it sort of works… Stabbing in the dark is part of the Grasshopper experience.

Another method for gradient points (culling) that makes more sense to me, and I’ve used it several times, is this one from January, 2024:

gradient_points_2024Jan17a.gh (28.6 KB)

It is based on Random Reduce in a range of “consecutive domains”.

I looked at the files in this thread but the GH file doesn’t seem to be connected to the hidden layer in the Rhino file. Did you make the connection yourself?

I can do that but… OK, I’ll stop whining now. This is a simplified variant of the idea:

gradient_2024Oct18a.gh (172.4 KB)

Geometry is internalized, no need for Rhino file.

P.S. The white group in version ‘b’ below sorts the branches by Z.

gradient_2024Oct18b.gh (174.7 KB)

Oops, I see an error…

[Joseph_Oster]

I thought I had something simple but lost it!

gradient_2024Oct18c_R7.gh (180.7 KB)

As before, geometry is internalized, no need for Rhino file.

Rats I just realized that because the Rhino file was R8, the Area component I used required R8. I just posted a replacement for R7 (and R8) but the file size jumped by 50K in the process So I quit and restarted Rhino several times and re-saved the file until its size dropped.

[Joseph_Oster]

This version ‘d’ tries to make it more understandable by sorting first and then, in the purple group, doing the random reduction by row. I don’t know for sure if either version is correct

gradient_2024Oct18d_R7.gh (183.0 KB)

NOTE: GH file size is 53K larger in R7 than when saved in R8

[Joseph_Oster]

For what it’s worth, a Graph Mapper can easily be added. The default graph is linear, exactly as it was without any Graph Mapper:

gradient_2024Oct19a_R7.gh (216.8 KB)

But as expected, shaping the graph alters the result:

gradient_2024Oct19b_R7.gh (216.9 KB)

[pennymag]

Thank you for taking the time to look this through and thank you for showing me another way of doing it!