emergence_3_documentation
Project: Emergence and Navigating Space
Project: Emergence and Navigating Space
the intention of the project was to create a somewhat complex colony of spheres using jared's box fitting code as the base code for th emergent process. for the most part, i was more intrigued by the visual process as opposed to the code itself (which i tweaked without a comprehensive understanding of its structure). what was most successful about the program was the unprecedented 'swarming' of the spheres in certain areas of the canvas. in jared's code, the rectangular boxes arrange themselves based on some kind of a collision/color detection. in my blind modification of jared's code, i unintentionally forged the attributes that jared had intended for rectangular boxes to spheres/ellipses. as a result, all hell broke loose when it came to collision detection, but surprisingly it yielded a pretty nice visual result. so this is essentially jared's box fitting code wrongfully applied to non-rectangular objects, and with additional variables and functions that control the flow, positioning, and outcome of the code.

/final print - recorded at the 107th frame

/preferred output - recorded at the 955th frame
final word: some things are designed to be viewed on the screen (preferably at resolutions under 1680x1050), and this emergence project turned out to be one of them. in print, there are particular areas in the final composition (which i did not intend the viewer to see) blown up to scale in high-res. moreover, the program could only run less than 1/7 the time of its desired length due to severe out-of-memory errors that keeps the program from rendering past the 107th frame. therefore, what is presented on screen here (in the second image) and in the previous posts are the preferred the representations of the project's outcome and visual process.

/final print - recorded at the 107th frame

/preferred output - recorded at the 955th frame
final word: some things are designed to be viewed on the screen (preferably at resolutions under 1680x1050), and this emergence project turned out to be one of them. in print, there are particular areas in the final composition (which i did not intend the viewer to see) blown up to scale in high-res. moreover, the program could only run less than 1/7 the time of its desired length due to severe out-of-memory errors that keeps the program from rendering past the 107th frame. therefore, what is presented on screen here (in the second image) and in the previous posts are the preferred the representations of the project's outcome and visual process.