CSCE 689-604: Special Topics in Multi-Robot Systems
Instructor: Dr. Dylan Shell
| Office | : | HRBB 333B |
| Phone | : | (979) 845-2369 |
| : | dshell_at_cs.tamu.edu | |
| Web | : | http://robots.cs.tamu.edu/dshell |
| Office hours | : | Thursdays after lectures or by email appointments |
Fall 2009
| Lecture Time | : | Tuesdays & Thursdays 5:30pm-6:45pm |
| Lecture Location | : | RICH 912B |
Course Description
Recent years have seen a great increase in the volume of research conducted into multi-robot systems. This course covers the state-of-the-art in control and synthesis techniques for multi-robot systems. Starting initially from motivations and definitions, students will study several important coordination methods and the ideas that have inspired them. The course balances study of fielded systems and applications with analysis of algorithms and formalisms. Students will use physical robots to design, implement and demonstrate multi-robot controllers.
Detailed Description
This course is a seminar-style survey of issues and approaches to control and coordination in multi-robot systems. Although the subject area is distributed robotics, it is an explicit goal of this course to advance students' critical thinking and communication skills. This is achieved through discussions, regular presentations and report writing.
Students will read original papers within the field, tracking the development from early seminal works, quickly gaining breadth through surveys, and sample particular approaches through representative systems. The discussion will focus on the multi-scale aspect of cooperative phenomena, i.e., high-level coordination and planning versus local real-time control and interactions. Throughout the semester, the course will consider both demonstrated multi-robot systems and biological and/or natural systems that have served as inspiration for these systems.
Students are expected to read all of the required readings. Each of the papers will be presented by an assigned student, and will be discussed and critiqued by everyone in the class. The students presenting a paper in a given class should prepare a clear 25-minute presentation. This presentation should assume that the audience has read the paper, and not spend more than about 5 minutes summarizing it. Most of the presentation should be spent on discussing the paper, its strengths, weaknesses, any points needing clarification, and addressing any questions. Students are encouraged to include videos and any other interesting supporting information in support of the presentations. For lectures in which additional readings are provided, these are optional to the class, but the presenters are expected to have some familiarity with the material.
Presentations require a PowerPoint/Foils presentation to show from the students' laptops. An LCD projector is available in the meeting classroom for the paper presentation it is the presenter's responsibility to provide the presentation on a laptop that is compatible with the projector, and cables to connect to it. Please plan ahead to address logistical questions.
For each paper being covered on a given day, each student (whether presenting or not), will bring to class a report up to one page long (no more), consisting of the following parts:
- A paragraph briefly summarizing the contributions of the paper (copies of the abstract and/or intro and/or conclusions will not do);
- A paragraph critiquing the paper. The critique should take the form of addressing the strengths and weaknesses of the paper, comparing it briefly to other work, especially other papers read in class, as relevant, etc.
The reports should be written in the same formal tone as the papers read in class; this means no contractions, jokes, or otherwise inappropriate expressions for a technical report. Eloquent prose and literary style are encouraged, as is originality of content, but keep in mind that these reports are one type of practice for technical writing. Further details can be found in this rubric which outlines aspects used in assessing the reports.
All summary reports should include: the student's name, and the title and authors of the paper being summarized and critiqued. Hand-written or late reports will not be accepted. Each paper report should be turned in on a separate piece of paper, i.e., do not bundle multiple reports due on a given day into a single report, turn them in as separate stand-alone reports.
In summary, for each class, you should bring:
- Printouts or digital versions of the papers being discussed;
- A printed summary report for each of the papers;
- A presentation, if you are presenting one of the papers;
- Great enthusiasm for discussing all of the papers.
Prerequisites
No particular course is a prerequisite, however, students will required to be proficient programmers in a language such as Java, C or C++. Familiarity with common Open Source Software and GNU/Linux will be beneficial. Students will need to demonstrate critical thinking and broader scientific skills (such as technical writing and presentation) throughout the course. Enrollment is open to all graduate students and undergraduate computer science seniors that are deemed competent.
Learning Goals
The following are the learning goals of this course:-
- Students will gain an understanding of state-of-the-art in multi-robot control and coordination techniques.
- Students appreciate the development and process by which the state-of-the-art has been arrived at.
- Students will hone critical thinking and communication skills (including technical discussion, presentation and writing).
Syllabus
Introduction & Motivation
"More Is Different", P. W. Anderson, Science, Vol. 177, No. 4047. (Aug. 4, 1972), pp. 393-396.
Early Demonstrations
"An imitation of life", W. Grey Walter, Scientific American (1950) 182(5): 42-45.
"A machine that learns'', W. Grey Walter, Scientific American (1951) 185(2): 60-63.
(Sept 3) Roozbeh Daneshvar
(Sept 3) Kevin Pratt
- "Vehicles. Experiments in Synthetic Psychology", V. Braitenberg, The MIT Press, 1984.
- "The first biologically inspired robots", O. Holland, Robotica, 21, pp. 351-363, 2003.
Principles of Control Architectures
(Sept 8) Abhishek Soni
Group Behavior: Minimalist Control
(Sept 10) Benjamin Fine
(Sept 10) Phillip Coleman
(Sept 15) Tanushree Mitra
- See book 5. (Available in digital form via the library.)
Group Behavior: Strategy
(Sept 22) Vasant Srinivasan
(Sept 24) Yong Song
(Sept 24) Lantao Liu
Optimal Assignment Problem
Group Behavior: Market-based methods
(Oct 1) Narayana Penukonda
- See book 4.
Task Domain: Motion Control, Planning, Formations
(Oct 6) Zohreh Keshavarzbagheri
(Oct 8) Dr. Shell
No class on Oct 13!
Task Domain: Tracking
(Oct 15) Shawn Kristek
Task Domain: Predator-Prey
(Oct 20) Brittany Duncan
Automated Synthesis
(Oct 22) Jung-Hwan Kim
Analysis
(Oct 27) Dr Shell
(Oct 29) Negar Rashidi
(Nov 3) Dr. Shell
- "On Information Invariants in Robotics." B. Donald, Artificial Intelligence --- Special Volume on Computational Research on Interaction and Agency, Part 1, 72(1-2):217-304, January 1995.
- "Communication Complexity of Multi-Robot Systems", E. Klavins, Algorithmic Foundations of Robotics V, volume 7 of Springer Tracts in Advanced Robotics, 2002, pp. 275-292.
Biological Inspirations
(Nov 5) Dongkun Kim
- "Ant Colony System: A Cooperative Learning Approach to the Traveling Salesman Problem", M. Dorigo and L. M. Gambardella, IEEE Transactions on Evolutionary Computation, 1(1): 53--66, 1997.
- "A Distributed Feedback Mechanism to Regulate Wall Construction by a Robotic Swarm", Robert L. Stewart and R. Andrew Russell, Adaptive Behavior, 14(1), 2006, pp. 21-51.
Coordination Primitives
(Nov 10) General Discussion
Simulation
(Nov 12) General Discussion
No class on Nov 17, Project Work.
No class on Nov 19, project work.
Nov 24: Meeting in the Lab to discuss project progress.
Learning Outcomes
By the end of the course, the student should be able to:-
- Understand and articulate the meaning of embodiment, situatedness and feedback in distributed robotics systems.
- Name several hard open-problems in the area, and understand why they are hard.
- Explain the dichotomy that currently exists between implicit and explicit coordination mechanisms, and provide examples.
- Give examples of how biology, operations research, and economics have inspired solutions to distributed robot problems.
- Position novel research within area of multi-robot systems.
- Give a technical talk.
- Write a high-quality review of multi-robot systems conference paper.
Texts
The readings are cited in full. Digital versions should be either easy to find, or available from the class website.
No textbooks are required. However students (and particularly presenters) may need to read more widely to gain a thorough understanding of the papers. The following books may be useful in this regard:-
- Introduction to AI Robotics, Robin Murphy, MIT Press, 2000.
- Autonomous Robots, George Bekey, MIT Press, 2006.
- Probabilistic Robotics, Sebastian Thurn, Wolfram Burgard and Dieter Fox, MIT Press, 2005.
- The Sciences of the Artificial, Herbert Simon, MIT Press, Third edition, 1996.
- Swarm intelligence: From Natural to Artificial Systems, Eric Bonabeau, Marco Dorigo, and Guy Theraulaz, MIT Press, 1999.
Course Projects
The principles learned in this class will be applied to a final experimental project that will include an implementation on physical robot hardware. In addition to this, there is an earlier mini-project, which will involve demonstration of a simple on a single physical robot.
It is expected that these aspects of the course will take a significant portion of each student's time. Students are strongly advised to start early so as to ensure completion.
Mini-Project
The instructor will provide a simple feedback behavior which students are to individually implement and demonstrate to the satisfaction of the instructor.
Final Project
Looking at teaming? This is what your classmates are looking for in collaborators.
A list of recommended individual projects will be provided by the instructor on request. (Some suggestions are here.) Students will have a fair degree of flexibility in that they can adapt those provided or even propose their own projects. Team projects are also possible, but with the following provisos: 1) teams must not exceed two students, 2) the project scope must be twice that of individual projects, 3) the individual contribution of each team member must be clear, and 4) individual final reports must be turned in. After proposal documents are submitted, feedback will be provided as well as a decision. Students (or groups) must have confirmation of an acceptance of the proposal. If the project proposal deadline passes without an accepted project proposal, the student must submit one of the original proposed projects.
Each project is expected to be an implementation of coordinated group behavior involving a complex interaction (e.g., cooperation on a task, competition, and/or adaptation) implemented on the iRobot Create hardware. Office hours will be used to iterate on proposed projects in person.
Final projects will be presented to the class on scheduled end-of-semester presentation days. Project presentations will be alloted 20 minutes, followed by questions from the class. Live demos are encouraged but not required
A detailed final paper is a required part of the course project. A hardcopy of the report is due on the last day of project presentations. Specification of the final paper will be provided in class.
The following are important project dates:-
| 8 September | : | Hardware provided and mini-project details provided during class. |
| 1 October | : | List of suggested final projects provided. |
| 6 October | : | Mini-project's due. |
| 15 October | : | Project proposals due. (Sooner acceptable too!) |
| 23 October | : | Deadline for accepted proposal. |
| 8-9 December (Finals week) | : | Project presentations and final papers due. |
Assessment and Examinations
Grades will be based on the following components:-
| Class Participation | : | 15% |
| Paper Summaries | : | 20% |
| Paper Presentations | : | 15% |
| Mini-Project | : | 10% |
| Final Project | : | 40% |
Notice, in particular, the significant weight given to class participation. As a seminar-style course, students are expected to have several serious critiques of the paper prepared for class and to miss few sessions. All students are granted two paper summaries that they can miss without penalty. Use those two wisely. Make-ups for assignments and projects will be given only under circumstances beyond student's control (a university sanctioned excuse). Unless circumstances are particularly extreme, it is expected that an absentee presenter shall find a suitable replacement. Prior arrangements with the instructor must be made when feasible and official verification of circumstances necessitating the absence will be required.
Please seek assistance immediately if you are having difficulty with the course. Help can only be made available from the instructor and the teaching assistants if they are notified promptly.
Students with Disabilities
The Americans with Disabilities Act (ADA) is a federal anti-discrimination statute that provides comprehensive civil rights protection for persons with disabilities. Among other things, this legislation requires that all students with disabilities be guaranteed a learning environment that provides for reasonable accommodation of their disabilities. If you believe you have a disability requiring an accommodation, please contact Disability Services, in Cain Hall, Room B118, or call (979) 845-1637. For additional information visit http://disability.tamu.edu.
Academic Integrity
This course has a zero-tolerance policy to academic misconduct of any kind including: cheating, fabrication, falsification, multiple submissions, plagiarism. Ignorance of the rules does not exclude any student from the requirements or the processes of the Honor System. Definitions and further information is at http://www.tamu.edu/aggiehonor. Note in particular the seriousness of the disciplinary action.