The SYMMETRY project
The process was long, this included drawing reflections, rotations, translations on a piece of paper. Then transferring it to a program called star logo to animate the movements. Star logo is a very simple coding program based on drag and click, with expressions such as IF, IFELSE, FOREVER, PROCEDURE. Things of that nature. It is mostly used (at least in my case) to draw X and Y lines, Reflections, Shapes, Rotations. The program can be really frustrating at times as things should work, but for some reason don't fit together or just absolutely does not work the way it is intended to. Although it has problems you can create interesting things.
The habit of a mathematician I used was persistence, most of the learning in star logo is frustration and annoyance (Atleast for me) most of it was a trial and error. Its really hard to think of something that went "well" because of all the random stupid moments this program has, but I'd have to say the final product looks pretty interesting. I understood what each piece of code meant, I just didn't know how or where they fit together, this is usually where I asked for help. This is why my final product looks and works almost exactly the same as some of my peers work. What did not go well? Quite a bit each benchmark was frustrating and I had to end up getting help form people. Mostly copying code studying it and then finally understanding how it works, although I really did enjoy the project it was different from what we normally do here.
Something I think could be done differently if this project is done in the future is to give people some more time. Most of the time we had packets with what we needed to do to complete the benchmark, but this didn't teach me anything all I knew is I needed to follow the packet. I believe that giving us more time would let us understand how some of these pieces of code connect. So that we have more unique and interesting code in the future, as most of the class's code could be related in some way.
The habit of a mathematician I used was persistence, most of the learning in star logo is frustration and annoyance (Atleast for me) most of it was a trial and error. Its really hard to think of something that went "well" because of all the random stupid moments this program has, but I'd have to say the final product looks pretty interesting. I understood what each piece of code meant, I just didn't know how or where they fit together, this is usually where I asked for help. This is why my final product looks and works almost exactly the same as some of my peers work. What did not go well? Quite a bit each benchmark was frustrating and I had to end up getting help form people. Mostly copying code studying it and then finally understanding how it works, although I really did enjoy the project it was different from what we normally do here.
Something I think could be done differently if this project is done in the future is to give people some more time. Most of the time we had packets with what we needed to do to complete the benchmark, but this didn't teach me anything all I knew is I needed to follow the packet. I believe that giving us more time would let us understand how some of these pieces of code connect. So that we have more unique and interesting code in the future, as most of the class's code could be related in some way.
Here is an image of my final product. As well with images of the final product code. (Download link below)
Here is my final product, Benchmark #7 as seen in the image above. Feel free to download it and do what ever you want with it.
benchamrk_7.sltng | |
File Size: | 16 kb |
File Type: | sltng |