From the course catalog:
An introduction to the design and implementation of intelligent mobile robot systems. This course will cover the fundamental elements of mobile robot systems from a computational standpoint. Issues such as software control architectures, sensor interpretation, map building and navigation will be covered, drawing from current research in the field. Students will also design and build a small mobile robot and program it to perform simple tasks in real-world environments. Class size limited to 20. Prerequisites: CSE 131/CS 101G, SSM 326A, Math 320 or permission of instructor.
| Smart: | by appointment |
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
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, up to a maximum of three days. If you're more than three days late on an assignment, you get zero points for that assignment. 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.
| Lab | Out | Due | Solution | |||
| Lab 1 |
September 2 | September 9, 23:59:59 | example solution | |||
| Lab 2 |
September 16 | September 23, 23:59:59 | ||||
| Lab 3 |
October 4 | October 16, 23:59:59 | ||||
| Lab 4 |
October 20 | October 28, 23:59:59 | ||||
| Lab 5 |
October 29 | November 6, 23:59:59 | ||||
| Lab 6 |
November 11 | November 25, 23:59:59 | ||||
| Lab 7 |
December 3 | December 15, 23:59:59 |
The example code for C++ that comes with Player is also available
locally on the CEC machines
at /usr/local/share/player/examples. The files needed
for Stage can be found in /usr/local/share/stage/worlds/
on the CEC linux machines.
Some useful links:
| Player Documentation | |
| Documentation for our real robots | |
| Documentation for our cameras | |
| Stage Documentation |
You will need to check the robots out from the CEC help desk. You are allowed to check the robot out for two hours, and must return it after that time. You're not allowed to check the robots out overnight (sorry). The help desk staff will keep all checked-in robots for one hour after they are checked in, to make sure that they can be fully recharged.
You can reserve time on a robot here. Do not reserve a robot within an hour of it being handed back, since the help-desk staff will not give it to you. If you know that you're not going to use a reservation, then please cancel it so that someone else can use the slot. You can get a robot without a reservation, if one is free, but it will help everyone in the class if you can plan your robot time in advance, and add it to the calendar.
Don't put personal stuff on the robots, since they are shared
machines, and you will be sharing an account with the rest of the
class. Either store things on a USB stick, or copy them on
via scp when you need them. In particular, please
remember to clean up the home directory, and to remove all of your
code before you turn the robot back in to the CEC help desk.
| Page written by Bill Smart. |