| Warning: The following information is for general information only. Each year the course is changed in different ways to react to student comments from the year before. If you have a CMU andrew account, the latest course webpage is available here. |
Instructor: Alonzo Kelly, NSH 3209
Prerequisites: There are no formal prerequisites for the course. However, you will get more out of the course if you have done computer vision and robot manipulation courses already. Robotics PhD students are automatically admitted. Other students are admitted subject to approval of the instructor. The curriculum is multidisciplinary. Background in various fields such as computer vision, control theory, robotic manipulation, and computer science will be helpful. Students lacking a sound background in mathematics and programming may not be qualified to take the course.
Text: There is no formal text for the course beyond the course notes.
Lectures: Mondays and Wednesdays 1:30 - 2:50, NSH 3002 (in 2005!)

Scope: The course covers aspects of perception, planning, control, position estimation, and mechanical configuration that are unique or common to mobile robot systems.
Level: The course is targetted to senior undergraduates and graduate level students. Emphasis will be given to fundamentals but, because there are no good texts yet, the research literature will be a source of content.
Grading: All students are graded to an equal standard regardless of the level of their anticipated degree. Grading is based on homework assignments and a term project according to the following breakdown:
Late Policy: You also have two choices of late policy
Choice 1. Any material handed in late will be subject to a grade reduction of 25% per day up to a maximum of 3 days. All material is due at the start of class. This policy makes it possible for us to hand out solutions to problems and go over them in class.
Choice 2. Anything can be handed in at any time up to the last day of classes but solutions will not be provided.
A few homework tasks will be assigned which are intended to expose the student to the hands on details of core ideas. There will be homework every 2-3 weeks and it should take about 12-18 hours for a well prepared student to do well on it.
Subject to our ability to make it happen, an updated version of the mobile robot simulator that has been used in the past will be made available. This will enhance the quality of the course, but it has to be available to everyone. Access to a Windows computer and Microsoft Visual C++ will be necessary for some homeworks. Alternately, we will port the simulator to Java and use public domain development tools but the real-time aspects of some homeworks may suffer.
Term projects will take the form of a substantial assignment on a topic very relevant to mobile robots. The project is intended to expose students to more detail in at least one area related to the field.
The lectures will develop the fundamentals of this emerging sub-field of robotics by calling on the experience of practitioners, the common themes of the literature, and relevant material from more basic fields such as computer vision, mathematics, and physics.
The order of the lectures follows one typical implementation path for mobile robots from simple to more complex capabilities. The first step, at least for a retrofitted vehicle, is to render the actuators computer controllable with hardware and software. Then, the vehicle can move. Next position feedback is provided by the addition of hardware and software. At this stage, the vehicle can follow a predetermined path "blindly". With the addition of perception hardware and software, the vehicle is now able to avoid obstacles, use landmarks for positioning, and follow environmental features such as a road. Finally, with the addition of strategic planning capabilities, the system can navigate freely and perform a complex function. The last part of the course is devoted to the case where a vehicle is custom designed to be a robot to serve a particular need.
In order to allow for student involvement, this schedule is subject to modification . Topics may be added, deleted, or moved as necessary to accomodate various constraints that cannot be predicted.
This year, term projects will be done in collaborative groups. Groups should include 5 people with deviations permitted for class sizes which are not multiples of 5. If you want to work with specific individuals you should make sure that all of you represent consistent project interests. We will ask each of you to rank order a set of project topics and then form you into groups based on your responses.
Groups are expected to organize themselves into an efficient team, elect a leader or come up with whatever strategy you need to resolve disputes, and to meet regularly to coordinate yourselves and update each other on status.
All term projects require groups to prepare an interim presentation (literature survey / tutorial) and to present and submit a final report. The topic does not necessarily have to be an area of active research but it does have to be a believable part of a core mobile robots university curriculum. Each project will involve two steps.
You must rank order topics not later than
Feb 7, (all you have to do is decide your preference). Survey
presentations take place Feb 21 or Feb 28. Final reports and
presentations of their contents are dues Apr 25.
Here is a tentative list of suggested topics. I will fill in the details later. Each group will be assigned to the instructor or TA in order to mentor you in the research process.