From the course catalog:
This course covers advanced topics from the theory and practice of mobile robotics. Students will read, present and discuss papers from the current research literature. There will be a substantial programming project, in which students implement and test ideas from the current research literature on one of the departmentīs research robot platforms. Prerequisites: CSE 550A and strong programming skills (preferably in C++).
Unless explicitly instructed otherwise, everything that you turn in for this course must be your own work. If you willfully misrepresent someone else's work as your own, you are guilty of cheating. Cheating, in any form, will not be tolerated in this class.If you are guilty of cheating on any assignment or exam, you will be penalized the number of points that the assignment is worth. For example, if you are guilty of cheating on an assignment worth 10 points, your score on that assignment will be -10. If you copy from anyone in the class both parties will be penalized, regardless of which direction the information flowed. Two or more instances of cheating in the course will result in a grade of F for the class, and will be referred to the School of Engineering Discipline Committee.
We will follow the guidelines of the University Undergradate Academic Integrity Policy, but we reserve the right to make the final determination of what constitutes cheating for this class. If you suspect that you may be entering an ambiguous situation, it is your responsibility to clarify it before the professor or TAs detect it. If in doubt, please ask
| Design and project plan: | 5 |
| Initial implementation: | 15 |
| Milestone: | 20 |
| Final system: | 20 |
| Project presentation and writeup: | 15 |
Grades in this class will be assigned as follows:
85% A 75% B 65% C 50% D 0% F
The late policy for the class is 10% per day late. If you have some valid reason for needing more time on an assignment, then you should contact me at least two days before the deadline to request an extension. Last-minute requests will only be met in exceptional circumstances.
| 1. | Gesture Interface for Lewis the Robot | Garg | |
| 2. | Real-Time Strategy Game Interface for Robots | Blakely | |
| 3. | Formation Control for Mobile Robot Groups | Simon | |
| 4. | Collaborative Multi-Robot Mapping | ||
| 5. | Expressive Actions for Mobile Robots | Wilson and Iyun | |
| 6. | Path-Planning Bake-off | ||
| 7. | Auction-Based Task Allocation | Jedynak | |
| 8. | Dynamic Tasking Bake-Off | ||
| 9. | Vision-Based Localization | Emrich and Martignoni (software), Heller (hardware) | |
| 10. | FastSLAM Implementation | Heckel | |
| 11. | Fast Visualizations of the World | ||
| 12. | Line Segment Mapping System | ||
| 13. | Learning Efficient Gaits for a Spider Robot | Sistar | |
| 14. | Tracking and Classifying People and Objects |
| Description | Due Date | ||
| 1. | Initial description and timeline | 8 Feb 2006, 23:59:59 |
The example code for C++ that comes with Player is also available locally. The files needed
for Stage can be found in /usr/local/share/stage/worlds/
on the CEC linux machines.
| Page written by Bill Smart. |