Flux.IO - Moving to the cloud

Early this year, I was invited with some colleagues to San Francisco to test a new technology called FLUX.IO. The idea behind flux is quite smart: You design a building using parametric tools and coding, like Grasshopper, Dynamo or GenerativeComponents. Instead to save your model and “code” in your hard drive you do it in a server. The good stuff is that the whole calculation is made by a server instead of your computer. In theory you could manage big volumes of data without worrying about your laptop-tablet ram capacities. The other advantage is to work remotely with your mates. Since the model is in the cloud, all team members can tackle the same model at the same time, from different locations. Currently Flux is more oriented into resolve interoperability problems with GH-Revit-Excel-Dynamo-Flux. Send and receive data from all flavours.

Flux interface: flow composer and the bowl designed

During the 2 days workshop at Flux office we developed an stadium with the structure, skin and bowl. Tim Meyers from HOK Kansas, and Me (London) were charge of the bowl. Before we get started we had a short introduction to use flux, the nodes and the interface. We also had a brief introduction to JavaScript the language to generate and modify the geometry in flux. I must say, was my first time in JavaScript, and I really like it, overall the technology behind the functions. In general, during the workshop, play with flux was very addictive in all sense.

Image during the workshop. planning the design.

The presentations. On the screen, the bowl and the main parameters to control the geometry.


Add a comment