algorithmic modeling for Rhino
Developed as a part of the http://www.florarobotica.eu/ project.
Tags:
Comment
Not really. To develop a workflow you need tools both to generate the geometry and analyze it as well as to develop some intermediate language to communicate with the agents, or to formalize their behavior. In the scope of the project I don't work directly with the agents, but rather with the geometrical part. This picture is showing a random weaving pattern, with proper meshing (for instance used in FEA) and it is a result of the generic weaving pattern solver which I'm working on currently. It is generic because at this point it just creates geometry, but later on it might (or not) take some part in developing the agents' language or assembly instructions. At some point we probably will write a paper on how it works exactly... Take a look at what Petras is doing with those meshes and Kangaroo/C# magic https://vimeo.com/187378890
Thanks for the link. So these are the paths of agents walking randomly avoiding collision with other agents? Or agents have any utility function? The video shows a predefined path, why yours is as it is?
Hi Mateusz,
what use does it have within the project?
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2025 Created by Scott Davidson. Powered by
You need to be a member of Grasshopper to add comments!