Difference between revisions of "2015 Project 2"
(→Overview) |
(→Resources and Ideas) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
How: Declare global/static variables in your main.c code and use those variables to communicate between players. | How: Declare global/static variables in your main.c code and use those variables to communicate between players. | ||
| + | |||
| + | What: This is up to you. Here are a few suggestions: | ||
| + | |||
| + | * Information about the location of the ball. | ||
| + | * Information about teammate locations. | ||
| + | * Information about opponent locations. | ||
| + | |||
| + | Whatever you communicate though, you should be sure to be able to vary its quality, detail or accuracy. As an example, you might add noise to the information that is communicated in a range from 0 to 100%. This variation will provide the basis for your scientific study. | ||
| + | |||
| + | ==Experiments== | ||
| + | |||
| + | Conduct a quantitative comparison of your two teams. There are several ways to do this. First, of course, you can play them against each other. You can also play them against one of the example provided teams and compare the results. | ||
| + | |||
| + | In either case, you should vary the quality of communication and evaluate quantitatively how that affects the results. | ||
| + | |||
| + | ==Resources and Ideas== | ||
| + | |||
| + | See this paper for examples of how to assess the importance of communication: https://smartech.gatech.edu/bitstream/handle/1853/22230/comm.pdf | ||
| + | |||
| + | ==What to Turn In== | ||
| + | |||
| + | Via t-square turn in attachments only: | ||
| + | |||
| + | * Your basic team code in a zip file: basic.zip | ||
| + | * Your communicating team code in communicating.zip | ||
| + | * Your report in report.pdf | ||
| + | |||
| + | You can write your code on any platform you like, but it must compile and run | ||
| + | on gekko.cc.gatech.edu (a standard CoC linux box). | ||
Latest revision as of 23:52, 15 February 2015
Contents
Overview
In this project you will develop two robot soccer teams. We will be investigating the utility of communication in this project, so you should create one team that communicates, and another that doesn't and compare the two. The comparison will be more interesting and effective if the two teams are very similar except for communication.
Both of your teams should be able to consistently beat the example "brutes" team.
All the details about how to implement an ascii soccer team are here: http://www.asciisoccer.org
How and what to communicate
How: Declare global/static variables in your main.c code and use those variables to communicate between players.
What: This is up to you. Here are a few suggestions:
- Information about the location of the ball.
- Information about teammate locations.
- Information about opponent locations.
Whatever you communicate though, you should be sure to be able to vary its quality, detail or accuracy. As an example, you might add noise to the information that is communicated in a range from 0 to 100%. This variation will provide the basis for your scientific study.
Experiments
Conduct a quantitative comparison of your two teams. There are several ways to do this. First, of course, you can play them against each other. You can also play them against one of the example provided teams and compare the results.
In either case, you should vary the quality of communication and evaluate quantitatively how that affects the results.
Resources and Ideas
See this paper for examples of how to assess the importance of communication: https://smartech.gatech.edu/bitstream/handle/1853/22230/comm.pdf
What to Turn In
Via t-square turn in attachments only:
- Your basic team code in a zip file: basic.zip
- Your communicating team code in communicating.zip
- Your report in report.pdf
You can write your code on any platform you like, but it must compile and run on gekko.cc.gatech.edu (a standard CoC linux box).
