Project Overview
In the beginning of this project, I was a little apprehensive, because I had never coded or calculated probability of coding before. It was scary, very confusing, and I needed a lot of help, but overall it was an amazing project. We were required to code an interactive game that included elements of probability on Star-logo Nova or Scratch, that we showed off at Exhibition. After Exhibition, we started learning how to actually calculate probability. We learned how to use area diagrams, theoretical probability, observed probabilities, tree diagrams, and two-way tables. We were expected to learn how to code, and then calculate the probability of the games we coded. I can confidently say that I have learned both of these things.
Project Process
In class, we started small. We began simple coding and activities in Star-logo Nova, experimenting and feeling our way around the program. Once we started on our benchmarks, things started moving pretty quickly. Benchmark #1 was a worksheet where we wrote down our initial ideas, to be improved upon. Benchmark #2 was a worksheet we were to fill out, detailing our game, how it was going to be played, what aspect of probability will be involved, and some challenges we might run into when creating our games. Benchmark #3 was cancelled, because it was essentially Benchmark #2. Benchmark #4 was postponed till after Benchmark #5. Benchmark #5 was the actual creation of the game in Star-loga Nova. It was two weeks of intense work time. We only had 1 hour each day, so we were cramming, lining up to Dr. Drew for help, and scrambling around trying to get answers from people making the same game. This was the final version that we had at Exhibition. Benchmark #4 was the analysis of the probability, using the skills we learned in the 2 weeks after we got back from winter break. Benchmark #6 was another analysis of all of the working components, but was cancelled due to lack of time. Benchmark #7 is updating, in detail, the project on our digital portfolios.
Game Description
My game, that I made in Star-logo Nova, was Hungry Hungry Elephants. Its just like Hungry Hungry Hippos, but with elephants. I would have done hippos, but there were no hippo avatars in Star-logo Nova. You start out with a blank, green canvas. You press the "Setup" button, then the "Shark Bait oohaha" button. There will be 4 elephants, all facing the center, all with colors randomly generated. In the center of the elephants, there will be a cluster of white spheres and fuchsia manta rays. (Image to the right)
|
After you press the "Setup" button, the spheres will float around the terrain. (Image to the left) When you hit the spacebar, all of the elephants step forward, then back. If the elephant hits one of the white spheres, the sphere will delete, and 10 points will be added to the score. If one of the elephants hits one of the manta rays, there will be a 1/10 chance that the elephant will get scared and disappear. That is my aspect of probability.
(Link to my game below) |
Reflection of Project
This project was very challenging, but I enjoyed it. It was a fun project. We were applying our creativity to coding, and then calculated probability to the code. I definitely had to stay organized throughout the project! That was one of the Habits of A Mathematician that I used every day. I had to keep track of benchmark due dates, the components of the benchmark that I needed to turn in (a lot of the times there were a couple), and complete all the aspects of the benchmarks, all while keeping up with homework and assignments from all my other classes. Not to mention the stress of impending doom (Exhibition)! The second Habit of a Mathematician that I used more than once in this project, was Trial and Error. There were many other game ideas before there was Hungry Hungry Elephants. I had to try and apply probability to each new idea, then try and translate it into Star-logop Nova, which was a nightmare. When coding, you can't just create something and tell it to stand off to the side. There is a lot more done than said. You need to create the actual thing, chose what color, shape, and size you want it to be, and find out the exact coordinates of the spot you want it to sit. If you want it to move, you need to program a certain number of steps forward, then decide if you want it to return to it's point of origin, and then figure out how to do that. It's a very complicated process, and it took about 4 days, trying to find a game that I could reasonably finish in the certain time and mathematical constraints.