The Evolution of Computational Design
In this article, Jeremy Graham, Computational Design Lead, Australia, discusses the evolution of computational design tools in the architecture industry and where they have the potential to take the field in the future. Quotes from Jeremy include:
On his definition of computational design
Say you wanted to generate a cube. There’ll be a series of steps that you’d go through to create it. You may have a starting point, you may have an outline of the cube, like the base rectangle, and then you may extrude that rectangle to arrive at an end object. Computational design is essentially automating or setting up an algorithm that goes through all of those steps. All we really need to do is change the input and we can get a different output. The input may be the location of the cube and the algorithm would be used to generate the cube at that location.
On what's unique about our data-driven design team
We’re a group made up of architects, data scientists, data engineers and industrial engineers. What that means is we’re doing computational design, but we’re not just doing it for form finding. We’re using it to extract and use public and private data to help inform objective design decision-making. It’s using the similar computational workflows that have been done in the past, but really augmenting that with data.
On democratising access to computational design
Many practices develop these scripts, but usually only one or two people have the knowledge to run them. A lot of the work I do now is allowing more people access. I develop bespoke tools that don’t require scripting or programming. Any planner can access them.