CS393R: Autonomous Robots -- Final Project

Final Project

NOTE: The dates have not yet been updated from the last course offering, but the structure of the project is intended to be the same.

 
Your final programming project is to do something interesting with the Nao robots. We encourage you to find a way to use the Naos - especially if you're potentially interested in contributing to our RoboCup team this spring. You may try to build on some of the research papers you have read about in the class; you may try to reimplement something you've found interesting that other teams have done; you try to do something that has never been done before; you may write new code from scratch; you may modify existing code. It's up to you!

You are encouraged to work in teams of 2. You may work individually if you prefer. Teams should only turn in one submission of the programming portion of the assignment. However, each person must turn in an independently-written proposal, survey, and final report.

The schedule is as follows.

  • Project Proposal due on Thursday, October 24th at 12:30pm.
    •     Submit a proposal as plain text by email to Jake and Peter, including:  
       
    The proposal should be written with the goal of convincing us that what you are proposing to do is interesting and non-trivial (though not necessarily completely original - see below). Members of 2-person teams should clearly identify what their roles will be with relation to the overall project.

    It is completely legitimate to propose to do something based on something you read about provided that you are going to do the coding yourself. Just make sure to acknowledge any ideas (and code) that you borrow and be sure to clearly identify what you are going to do.

    Be as specific as you can at this point. The more specific you are, the more detailed feedback you will get.
  • Literature Survey due on Thursday, November 14th at 12:30pm.
    •     Submit a literature survey of the work most closely related to your project to Jake and Peter. It should begin with a summary of your current plans for the final project. If nothing has changed since the proposal, you can use the same text. If you have changed your plans in some way, please specify how and why. Then the survey should include at least 10 references, some of which can be from the class readings. For each, you should discuss how it differs from or is similar to the work you plan to turn in for your final project. A good survey discusses each of the references at a technical level - not just what is done, but also how. Please put the references at the end, with full reference information (authors, title, date, publication venue, etc.). I suggest writing this as if it were a section of a research paper, so that you can then use it directly in your final report. 
  • Your final Project due on Tuesday and Thursday, December 3rd and December 5th at 12:30pm.
       Submit your final project including:

  • Source code and executable (Tuesday). 
  • A README providing a brief guide to following your code (including which files are most relevant to look at, etc.). Make sure it is absolutely clear how to run your code. (Tuesday)
  • A detailed written report describing your project, including its merits, and its deficincies. As much as possible, you should relate your approach to the readings from throughout the course. View this report as a term paper. It is in place of a final exam and will be a large factor in your final grade for the project and for the course. The report should be roughly in the style of a conference paper, including introduction, motivation, related work, etc. (Thursday)
  • Members of teams should clearly identify what their roles have been in relation to the overall project. All writing should be your own -- even if you are describing a component produced by your partner.
  • Include at least 10 citations with full bibliographic references to acknowledge where your ideas came from.
  • Be very clear about what code you've used from other sources, if any. Clear citations are essential. Failure to credit ideas and code from external sources is cheating.
  • Make sure you evaluate both the good and bad points of your approach.
  • Show results of at least one experiment evaluating some aspect of or your entire approach, preferably showing error bars or some sort of statistical measure of the significance. Even if you didn't accomplish your goal, evaluate what you did do.
  • If any parameteres are mentioned in the report, be sure to mention how you arrived at their values. Was it the first thing you tried? Trial and error? Roughly how many trials? etc.
  • Remember to proofread and spell-check!
  • Project demos in class on Tuesday and Thursday, December 3rd and December 5th at 12:30pm.

  • Prepare to describe your project to your classmates.
    • [Back to Class Homepage]

    Page maintained by Peter Stone and Jake Genter
    Questions? Send me mail