christopher

[caption id="attachment_614" align="alignnone" width="450" caption="L-system graphically mapped"][/caption] [caption id="attachment_656" align="alignnone" width="450" caption="hah this is what its supposed to look like"][/caption] [caption id="attachment_615" align="alignnone" width="450" caption="The Lizard"][/caption] [caption id="attachment_631" align="alignnone" width="450" caption="The Scorpion"][/caption] [caption id="attachment_616" align="alignnone" width="449" caption="The stingray"][/caption] [caption id="attachment_617" align="alignnone" width="450" caption="the Final? outcome, if there ever is a final product"][/caption] [caption id="attachment_618" align="alignnone" width="450" caption="view of the top"][/caption] [caption id="attachment_619" align="alignnone" width="450" caption="view from below"][/caption] To create these models I researched L-Systems, and was intrigued by using the generational code to create a "landscape" After mapping out my L-System with my chosen rule set, I assigned a value to each corresponding piece of combination of pieces of the code. When creating the models, I chose to create an 'L-System Navigator' which would follow the code, and when a certain combination of code was reached it would split, one side would continue the path, the other would move to the next generation and continue.