A part of computational design that interests me is eliminating, or minimizing, repetitive actions in a workflow. Something simple and frequent that I encounter in AutoCAD is a shift in a wall’s position; an inevitability. If additional drawings exist that are based on the position of walls, then all related drawings must be updated to conform to the changes. Rather than working with drawings that have line work that is disconnected, I prefer to work with and setup drawings that are interdependent, tied together with geometric and design logic.

In the past few weeks I have done a lot of reshuffling of Archbot, with a near complete overhaul of the code. It has changed to be more elegant, efficient, and flexible, with the core concepts still intact. I am using Google’s Flux to help divide many of the tasks among a collection of GH files, separating processing that responds to fixed variables (building program) from processing that responds to design inputs (adjacency, perimeter, directional placement, etc.). This allows the algorithm to respond to real-time inputs with greater ease, a necessity I have mentioned before.