Mesh pattern/ segmentation for fabrication

Lunchbox plugin also have K-Means Clustering component try that too.
Image courtesy: Nathan Miller


Yup it is the same Accord.NET library

Thanks @laurent_delrieu @Petras_Vestartas
Anyone can explain about this

by parallel agent-based search protocol, the non-linear stripes are the result of the indecisive behavior of the agents, which change their attitudes in tight turns. As they come together at seams and make their way to the ground, they find alignment as linear stripes. Across the ballooning expanses, they express the recursive quality of the computational description. Bifurcations and splits in the pattern tighten and spread to produce porosity. Like bubblegum blown just to the point of popping, the skin becomes thinner and more open across the wider expanses of the spheres, allowing light to come through. Where the volumes merge, the stripes between them become more densely packed, lending to the structural performance.
Mainly about parallel agent’s

These text’s are from theverymany website

1 Like

What I can discern in the upper reference image is that the base mesh is a collection of simple platonic solids. I guess, these spheres are distributed to look like a cloud. Bigger spheres seem to form the cloud center, whereas somewhat smaller ones occupy its periphery.
In the lower image, modified, stilted spheres are added. Some seem to be open meshes, like the columns in Zaha Hadid’s Serpentine Sackler Gallery expansion.
The first challenge is to unify the individual geometries into a single, clean base mesh with a quad tessellation and soft transitions. This could be done by re-meshing the geometries with Starling. Note though, how the topology of the base mesh is already very carefully designed. The stilts seem to feature a vertically oriented diamond tessellation.

The resulting new base mesh is then segmented into developable strips, probably with one of the approaches described by @laurent_delrieu above, to form the blue mesh segments of the substructure.
Note, how the segmentation seems to follow a rule, where there must be unselected mesh faces between two or more adjacent segments. The individual segments seem to be offset and thus aren’t interconnected, which renders this secondary structure unsuitable for development.

And here’s where the structural, primary shell comes into play, which stitches it all together!
It seems to be based on agent-based design, as described in the referenced text.
There are some plugins like Kangaroo 2, the BOID Library that is usually used in combination with Anemone, Quela, Culebra, etc. that can all handle agents, but scripting (e.g. Python, C#, Visual Basic) is always more flexible, especially if you want to incorporate intrinsic rules.
The agents start at the bottom of the stilts and in the connective valleys in-between the previously individual sphere geometries of the base mesh.
Their main mission seems to be to form developable bridging strips over the above mentioned individual strips of the blue substructure, thus rendering the cloud statically sound.
At the stilts, the agents produce very dense strips (light blue) that cover the entire surface of the base mesh and seem to be all interconnected.
In the connective zones, the agents also produce denser strips (violet), but leave some breathing room in-between.
The light blue and violet strips surely form the primary supporting structure, over the blue substructure.
The rest of the base mesh, gets more loosely covered in yellow strips, which probably only have a secondary structural role, apart from holding the strips of the substructure underneath together.

1 Like

As said by PirateBoy, agents are used to fullfill many constraints
Solidity => maximize intersection at right angle between lower and upper
Fabricability => Folding perpandicular to the plate
Fabricability => maximum length
Fabricability => unrollability

Thanks all I’ll work on it.


I still find it difficult to understand the process of reaching that! … How can I understand the steps to achieve it?