Game of Life *
*Note: This is an abbreviated Project Idea, without notes to start your background research, a specific list of materials, or a procedure for how to do the experiment. You can identify abbreviated Project Ideas by the asterisk at the end of the title. If you want a Project Idea with full instructions, please pick one without an asterisk.
Abstract
The Game of Life is the invention of the mathematician John Conway. It is a cellular automaton, consisting of a grid of squares that turn "on" or "off" depending on simple mathematical rules that involve neighboring squares. Depending on how the grid is first set up (i.e., the initial conditions), various interesting patterns appear. Can you write a Game of Life program (in JavaScript or any other computer language of your choice)? Can you think of ways to alter the rules that result in different patterns forming? Can you predict how the change in rules will change the patterns? Was your prediction correct? For more information on the Game of Life, see: Martin, E., date unknown. "John Conway's Game of Life," [accessed March 30, 2006] http://www.bitstorm.org/gameoflife/. (Suggested by Adam Schepis, Symantec.)Share your story with Science Buddies!
I Did This Project!
Please log in and let us know how things went.
Last edit date: 2013-01-10
Share your story with Science Buddies!
I Did This Project!
Please log in and let us know how things went.
Ask an Expert
The Ask an Expert Forum is intended to be a place where students can go to find answers to science questions that they have been unable to find using other resources. If you have specific questions about your science fair project or science fair, our team of volunteer scientists can help. Our Experts won't do the work for you, but they will make suggestions, offer guidance, and help you troubleshoot.Ask an Expert
Related Links
If you like this project, you might enjoy exploring these related careers:
Computer Programmer
Computers are essential tools in the modern world, handling everything from traffic control, car welding, movie animation, shipping, aircraft design, and social networking to book publishing, business management, music mixing, health care, agriculture, and online shopping. Computer programmers are the people who write the instructions that tell computers what to do. Read more
Mathematician
Mathematicians are part of an ancient tradition of searching for patterns, conjecturing, and figuring out truths based on rigorous deduction. Some mathematicians focus on purely theoretical problems, with no obvious or immediate applications, except to advance our understanding of mathematics, while others focus on applied mathematics, where they try to solve problems in economics, business, science, physics, or engineering. Read more
Computer Hardware Engineer
Whether you are playing video games, surfing the Internet, or writing a term paper, computers are an integral part of our daily lives. Computer hardware engineers work to make computers faster, more robust, and more cost-effective. They design the microprocessor chips that make your computer function, along with the equipment that makes computing easy and fun to do. Read more
Software Quality Assurance Engineer & Tester
Software quality assurance engineers and testers oversee the quality of a piece of software's development over its entire life cycle. Their goal is to see to it that the final product meets the customer's requirements and expectations in both performance and value. During the software life cycle, they verify (officially state) that it is possible for the software to accomplish certain tasks. They detect problems that exist in the process of developing the software, or in the product itself. They try and make things not work (try to "break" the software) by creating errors or combinations of errors that a user might make. For example, if a user enters a period or a pound sign for a password, will that break the software? They seek to anticipate potential issues with the software before they become visible. At the end of the life cycle, they reflect upon how problems or bugs arose, and figure out ways to make the software development process better in the future. Read more
