I have been cobbling together a script to create a standard stretcher brick bond along a surface, but with increasing bond spacing along the positive Z axis. The effect this creates is a single wythe brick wall which turns into a screen higher up on the wall.
My issue is this: Certain points in the wall are working out as a standard stacked bond, about every 5 rows. I am at a loss at how to adjust brick spacing for those rows alone, as I do not want to insert half bricks or anything which corrupts the stretcher bond. Presumably, I would need to either increase or decrease the spacing between bricks for these rows alone. I was trying to modify the culling bricks method of Joseph Oster, rather than doing a dispatch pattern on the list of HFrames, in order to get the stretcher bond in hopes that this could be modified to prevent this issue. However, I still couldn’t get this to work.
VariableBrickSpacing Edited v0.gh (28.1 KB) Plugin: Flexibility
It is such an important function in real - world fabrication. I wish it could be a native component.
I did this a couple of days ago and hoped to “fix it” before posting, but have failed so far. It is different from the “culling bricks” method. For several reasons, brick patterns can be difficult when each row has a different number of bricks.
I’ve thought about it and by nature of the problem (With the input surface I have set up) I have intersecting values leading to the overlap. The contour curves are DECREASING in length along positive Z, while the brick spacing is INCREASING along positive Z. Interferences are impossible(?) to avoid without nudging individual bricks based on their position in relation to others. So, difficult just like you said.
What you have is an interesting method though, I’ll have to take a further look later next week, as this project has been back-burnered. I have a feeling this will be a C# sort of problem in the end…
Thanks for the help!
P.P.S. ‘Min’ slider = 0.333 doesn’t look too bad either… Not quite there yet though. In GH, the correct algorithm is only half the battle - parameter values are the other half.
