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.
| Paul Spiegel (pas4@cec.wustl.edu) |
| Brian Heinz (bdh3@cec.wustl.edu) |
| Urbauer 115 | TBA |
| Lopata 400 (Linux Lab) | TBA |
| Smart: | TBD |
| Spiegel: | Tuesday, 1pm to 3pm Thursday, 1pm to 3pm |
| Heinz: | Monday, 2:30pm to 3:30pm Tuesday, 4pm to 5:30pm |
The grading staff will monitor the newsgroup and attempt to answer questions as quickly as possible. However, any technical questions mailed directly to the instructor or the TAs will be ignored. If you have a specific problem, then it's likely that someone else does too. Asking the question on the newsgroup archives the answer, and it means that the grading staff doesn't need to answer the same question 40 times.
Get into the habit of reading the newsgroup daily. Important messages about the class will be posted there. "But I didn't read the newsgroup" is not a valid excuse. If you have a problem reading the newsgroup, then let us know immediately.
Obviously, if you have a question or concern of a personal nature, you should mail this directly to the TAs or the instructor. Also, bear in mind the academic integrity policy when posting and answering on the newsgroup. If you have any doubts about the content of a question or answer, send email to the instructor and ask.
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.
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. |