Tuesday, March 22, 2011

Galapagos-Ecotect

I have a Celeron Dual Core T3000 1,8 GHz and 3 gig ram. This is way too slow too handle the optimisation of the flat part. The calculation of ecotect is quite heavy and requires more power. Our ´progressive seek algorithm´ does not have much impact on the results, because the population-size is too small. But we cant make it higher because the calculation-time would become too high. Days or even weeks.


Unable to display content. Adobe Flash is required. Here is an movie of the seekingprocess of only 4 of the 16 'islands'. It is speedened up 9 times (!). so the real proces took half an hour.

As you can see the population-size is low, and the optimum it finds is a clustering of dwellings. This is not the optimal solution, we can tell by common sense. Also earlier calculation with a higher ecotect-grid resolution, show that the optimal configuration for 2 of the blocks is this:

Compared to the optimum of the movie, this looks like its more optimal: more light enters the built space, because there are more surfaces facing open space. This shows that, with a high resolution grid and a bigger population size, the optimization works. But we lack the computational power to do the calculation...which is a shame. The bottleneck is the slow calculation of ecotect. Which is really frustrating.

1 comment:

  1. hello WAN
    i am quite interested in your galapagos-ecotect method , and i have some technical question about it . Have you used GECO(an plug'in for grasshopper)to link ecotect? if not ,how do you link ecotect and send back the message to rhino?

    ReplyDelete