CS393R: Autonomous Robots -- 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
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 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.
- Proposed starting point. That is, what code base will you be starting with? What would you like us to provide you with that you don't already have (No
guarantees you'll get what you ask for, but we'll try.)
- What you plan to do and how you plan to do it.
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
Be as specific as you can at this point. The more specific you are, the more detailed feedback you will get.
[Back to Class Homepage]
Page maintained by
Peter Stone and Jake Genter
Questions? Send me