Instructor: Todd Hester
Department of Computer Science
office hour: Wednesday 9:45-10:45 AM, Friday 1-2 PM, or by appointment
office: GDC 3.418
email: todd AT cs.utexas.edu
office hours: Tuesday 11 AM to Noon, Friday 2-3 PM
location: GDC 3.414B (BWI Lab)
email: shweta.gulati AT utexas.edu
office hours: Monday and Wednesday 3-5 PM
location: GDC 3.414B (BWI Lab)
email: j.munoz802 AT gmail.com
office hours: Tuesday and Thursday 2-4 PM
location: GDC 3.414B (BWI Lab)
email: britishnickk AT gmail.com
Good programming skills, preferably in C and/or C++. Some background in artificial intelligence is recommended but not essential.
Reading, written, and programming assignments will be updated in the table below. A tentative schedule for the entire semester is posted. But the readings and exercises may change up until the Tuesday before they are due (1 week in advance).
You can go directly to the final project page. To see your grades go to Blackboard.
Please enroll in the class on Piazza.
The class is listed as CS378B as Piazza only allows one class to have the CS378 number.
Important class information may be sent to this list. It is the student's responsibility to be subscribed.
The class will also make extensive use of a wiki. Reading responses, project updates, and other project information will be posted on the class wiki: http://farnsworth.csres.utexas.edu/bwi/index.php/CS378/Main_Page
The foremost goal of this course is to expose the student to the full range of activities required of a real-life computer science researcher. It turns out that computer scientists rarely read textbooks, sit silently in lectures, work on programming assignments with correct and complete answers, or take exams. Rather, they
This course presents an opportunity for students to help decide whether they would enjoy going on to graduate school and an eventual career as a computer science researcher. In particular, students will be required to read published research papers, write brief reactions to them, participate in class discussions, propose and execute a solution to a challenging open-ended problem, and write about their work. They will be given an opportunity to collaborate with other students on the final project.
This course is focused on developing a building wide intelligence (BWI) for the new computer science building. The idea is to have a pervasive intelligence throughout the building, in the form of robots, kiosks, display screens, and cameras. These robots will perform a variety of tasks, such as leading people to their destinations or locating a person in the building.
The main goal of this course is to complete a small research project, advancing the abilities of the current BWI system.
There will be incremental programming assignments to introduce students to the robots and the existing codebase. These will lead to a final project on the robots. Students are encouraged to work in groups for the last programming assignment and the final project.
Participation in the class discussions will also form a significant part of the grade. Class meetings will consist of discussions based on assigned readings and updates on project progress.
These deadlines are designed both to encourage you to do the readings before class and also to allow us to incorporate some of your responses into the class discussions.
If you turn in your assignment late, expect points to be deducted. No exceptions will be made for the written responses to readings-based questions (subject to the ``notice about missed work due to religious holy days'' below). For other assignments, extensions will be considered on a case-by-case basis, but in most cases they will not be granted.
For the penalties on responses to the readings see above (under course requirements). For other assignments, by default, 5 points (out of 100) will be deducted for lateness for the first two days, plus an additional 1 point for every additional 24-hour period beyond 2 that the assignment is late. For example, an assignment due at 2pm on Tuesday will have 5 points deducted if it is turned in late but before 2pm on Thursday. It will have 6 points deducted if it is turned in by 2pm Friday, etc.
The greater the advance notice of a need for an extension, the greater the likelihood of leniency.
All work ideas, quotes, and code fragments that originate from elsewhere must be cited according to standard academic practice. Students caught cheating will automatically fail the course. If in doubt, look at the departmental guidelines and/or ask.
The University of Texas at Austin provides upon request appropriate academic accommodations for qualified students with disabilities. To determine if you qualify, please contact the Dean of Students at 471-6529; 471-4641 TTY. If they certify your needs, I will work with you to make appropriate arrangements.
A student who misses an examination, work assignment, or other project due to the observance of a religious holy day will be given an opportunity to complete the work missed within a reasonable time after the absence, provided that he or she has properly notified the instructor. It is the policy of the University of Texas at Austin that the student must notify the instructor at least fourteen days prior to the classes scheduled on dates he or she will be absent to observe a religious holy day. For religious holy days that fall within the first two weeks of the semester, the notice should be given on the first day of the semester. The student will not be penalized for these excused absences, but the instructor may appropriately respond if the student fails to complete satisfactorily the missed assignment or examination within a reasonable time after the excused absence.
|Week||Date||Topic (Link to Slides)||Reading Due||Assignment Due|
|1||1/17||Hardware Overview||Sign up for piazza & wiki|
|2||1/22||Hardware / CoBot||
Stephanie Rosenthal, Joydeep Biswas, Manuela M. Veloso.
"An Effective Personal Mobile Robot Agent Through Symbiotic Human-Robot Interaction."
International Conference on Autonomous Agents and Multiagent Systems (AAMAS 2010).
|2||1/24||NO CLASS, Go to talk:
1pm, ACES 2.402
|Sign up for github|
|3||1/31||ROS Tutorial||Programming Asst. 1 (intro)|
|4||2/7||Meet in GDC 3.414B!||Post Teammate Search on Piazza|
|6||2/21||Project Ideas||Programming Asst 2 (Robot)|
|7||2/26||Proposal / Readings|
|10||3/28||Symposium Summary||Progress Report|
|13||4/16||Human Robot Interaction|
|15||5/2||Course Recap||Final Project|
|Finals||5/10||Final Demo Video||Final Project Video|
Page maintained by
Questions? Send me mail