REMEMBER: Shoham paper and chapters for FHMV are in a manilla folder in the ATL mailroom. MAKE YOUR OWN PERSONAL COPY AND PUT THE ORIGINALS BACK PROMPTLY FOR THE NEXT PERSON!
NOTE: Readings for the week of 3/29 have been revised!!
Assignment 7 is posted in the assignments directory. It is due 3/31/99.
Office hours have been added Mondays 1-3pm.
Lectures: Monday and Wednesday, 10:30-12:30, 3437 EECS
Instructor:
Edmund H. DurfeeEECS 492, or equivalent. We assume a solid grounding in search, logic, planning, uncertainty reasoning, and learning. We will take an "agent-based" approach.
This course has two main purposes. One is to provide students who want to become AI researchers and practitioners with a deeper and broader appreciation of the field. The other is to give students experience in reading and understanding cutting-edge research results as presented in recent papers rather than in textbook form. Students will demonstrate mastery of both of these goals by working through exercises, critiquing papers, discussing ideas and approaches in class, and completing a course project. By achieving both of these goals, students should be better prepared in AI breadth (for qualifying exams, for example) and in AI research methods.
Whereas it used to be that AI advanced topics could only be gleaned from current research publications, recently there have begun to emerge textbook treatments on these topics. For this class, we will use a combination of textbook treatments and research publications. The principle textbook will be the one used in the Intro AI course (EECS 492):
Stuart Russell and Peter Norvig,
Artificial Intelligence: A Modern Approach, Prentice-Hall, 1995.Supplemental reading will come from other books, including:
Fagin, Halpern, Moses, and Vardi, Reasoning About Knowledge, MIT Press, 1995.
Weiss, Multiagent Systems. A Modern Approach to Distributed Artificial Intelligence, MIT Press, in press.
Beyond that, we will read recent research papers on a variety of the topics covered in these books. A mechanism for acquiring these papers will be developed shortly after class begins.
At http://ai.eecs.umich.edu/people/durfee/courses/592winter99 you will find any files needed for assignments , as well as course handouts, syllabus updates, and all sorts of other useful stuff.
Many of the readings are available online. The Journal of AI Research (JAIR) has all of its papers online at
http://www.cs.washington.edu/research/jair/home.html. The Artificial Intelligence Journal (AIJ) has papers available to University of Michigan users through the U of M Digital Library's PEAK project at http://www.umdl.umich.edu/peak. Older papers from AIJ can sometimes be found by navigating through Elsevier's site at http://www.elsevier.com.During the meetings of this course, we will alternate (irregularly) between studying "textbook-like" treatments of topics, and then delving into research papers dealing with these topics. The textbook-like treatments are intended to give a somewhat balanced view of fundamental issues and approaches, while the papers give a more narrow and deep view of a vein of research within the topic. Thus, the former increases a student's literacy in core AI concepts and techniques, while the latter exposes the student to advanced issues as well as methodologies in AI research and development.
As a participant in this graduate level course, you are expected to not only soak up knowledge but also contribute to the knowledge gained by your classmates (and quite possibly your instructor). To this end, the course requirements include a combination of mastery of the material and going beyond it. Mastery of the material will be demonstrated through homework assignments and contributions in class. Going beyond will be demonstrated through a course project, as well as through some of the assignments and contributions in class.
Homework assignments will typically take one of two forms. One form is the standard "problem set" model, where you will be asked to solve some problems to develop facility with concepts, algorithms, and techniques we have covered. A second form is the "critique" model, where you are to write a short (no more than 1 page) critique of a paper or other piece of work. A critique represents your thoughts on the work (not a simple listing of the contents of the work) conveying:
You are expected to complete a course project to get a deeper "hands-on" feel for the material. Generally, what is expected is that you will find, during the course, some idea(s) that interest you, and that you will pursue that/those idea(s). This generally takes the form of duplicating some research results that we learn about in class, and extending them to address some limitations or to examine their strengths and weaknesses on other problems. Reports backed up by implemented programs, empirical testing, or mathematical analyses will be received especially favorably. The project should be substantial but not overwhelming, with a 10-15 page writeup (excluding code, traces, proofs, etc.).
As a graduate student studying advanced AI concepts, you will discover that the ideas, techniques, and methodologies at the frontier of the field are not always as straightforward to grasp and apply as the more established introductory ideas in the field. That is the excitement at the frontier! You are not supposed to simply treat whatever you read as being gospel; rather, you are to analyze and question it. A big part of moving on to advanced AI topics is to develop this inquisitiveness; to engage in discussions and debates about ideas and techniques.
Therefore, we expect and strongly encourage students to raise questions, voice concerns, and (best of all) make suggestions about the tools and techniques we will study. Do not assume that the authors, nor the instructor, have all the answers!! Contribute your answers. To encourage this, you will have a fraction of your grade based on the quantity and quality of your participatory remarks in class. It is thus crucial that you do the readings before class meets, and attend class!
Course grades will be based on performance on (approximately weekly) assignments, on a course project, on a (take-home) final exam, and on class participation. The tentative grade breakdown is:
Assignments are due at the beginning of class on the day specified by the assignment. This is especially important because some assignments are expected to establish literacy for the lecture/discussion topic; failure to submit the assignment on time will result in being underprepared for class discussion which will harm your grade on a couple of fronts.
We expect adherence to the Engineering Honor Code in all assignments and exams. All problem sets (home work assignments) are to be completed on your own. You are encouraged to discuss ideas and techniques broadly with other class members, but all written work, whether in scrap or final form, are to be generated by you working alone unless otherwise expressly stated in the homework assignment. You are not allowed to sit together and work out the details of the problems with anyone. You are not allowed to discuss the problem set with previous class members, nor anyone else who has significant knowledge of the details of the problem set. Nor should you compare your written solutions, whether in scrap paper form, or your final work product, to other students (and vice versa). You are also not allowed to posess, look at, use, or in anyway derive advantage from the existence of solutions prepared in prior years, whether these solutions were former students' work product or copies of solutions that had been made available by instructors. Violation of this policy is grounds to initiate an action that would be filed with the Dean's office and would come before the College of Engineering's Honor Council. If you find any ambiguity about this policy, it is your responsibility to contact the course staff.
Unless arrangements have been made ahead of time, late assignments will not be accepted. You are permitted to skip one assignment (other than the project!) over the course of the semester.
To be incrementally and interactively elaborated. Readings are: RN (Russell and Norvig); FHMV (Fagin et al); W (Weiss); JAIR (Journal of AI Research); AIJ (Artificial Intelligence Journal)
|
Day |
Month |
Topic |
Reading |
|
6 |
Jan |
Introduction and Overview |
FHMV 1 and others |
|
11 |
Jan |
Knowledge Bases |
RN 8.0 - 8.3 |
|
13 |
Jan |
Ontologies |
RN 8.4 - 8.6 |
|
20 |
Jan |
Temporal Reasoning |
Beek/Manchak JAIR 4:1-18 1996 |
|
25 |
Jan |
Constraint Satisfaction |
Ginsberg JAIR 1: 25-46 |
|
27 |
Jan |
Practical Reasoning Systems |
RN 10 |
|
1 |
Feb |
State-of-the-art Planning |
|
|
3 |
Feb |
Off-line vs On-line reasoning |
Moses/Tennenholtz AIJ 83:229-239 |
|
8 |
Feb |
Resource-bounded reasoning |
Zilberstein/Russell AIJ 82:181-213 1996 |
|
10 |
Feb |
Resource-bounded reasoning |
Musliner et al. AIJ 74:83-127 |
|
15 |
Feb |
Real-time AI |
RN 4.3 Russell/Subramanian JAIR 2:575-609 1995 |
|
17 |
Feb |
Hierarchy and Abstraction |
RN12.2 - 12.3 Bacchus/Yang AIJ 71:43-100 1994 |
|
22 |
Feb |
Hierarchical A* |
|
|
24 |
Feb |
Complex Decisionmaking |
RN 16.5-16.7 Heckerman/Schacter JAIR 3:405-430 |
|
8 |
Mar |
Sequential Decisionmaking |
RN 17 |
|
10 |
Mar |
Dynamic Belief Networks |
|
|
15 |
Mar |
POMDPs |
|
|
17 |
Mar |
Communicative Actions |
RN22 |
|
22 |
Mar |
Agent languages/semantics |
|
|
24 |
Mar |
Cooperative problem solving and planning |
Weiss Chapter3 |
|
29 |
Mar |
Agent-Oriented Programming |
Shoham "Agent-Oriented Programming" AIJ 60:51-92 (1993) |
|
31 |
Mar |
Agent-oriented Systems |
Jennings "Controlling cooperative problem solving in industrial.." AIJ 75:195-240 (1995) |
|
5 |
Apr |
Distributed Knowledge |
FHMV 1+2 |
|
7 |
Apr |
Rationality in MultiAgent Systems |
Weiss Chapter5 |
|
12 |
Apr |
Market-Oriented Systems |
Wellman JAIR 1:1 |
|
14 |
Apr |
Negotiation and Mechanism Design |
Zlotkin and Rosenschein AIJ 86(2):195-244 1996. |
|
19 |
Apr |
Project summaries |
|