http://www.cse.buffalo.edu/~rapaport/572/S97/syl.html
)
CLASS | INSTRUCTOR | REGIS. NO. | DAYS | HOURS | LOCATION |
---|---|---|---|---|---|
Lecture | Rapaport | CS 472: 457249 CS 572: 456180 | TTh | 9:30 a.m.-10:50 a.m. | NatSci 210 |
Recitation R1 | Campos | CS 472: 434139 CS 572: 379380 | T | 8:30 a.m.-9:20 a.m. | NatSci 210 |
Recitation R2 | CS 472: 286866 CS 572: 091612 | F | 2:00 p.m.-2:50 p.m. CANCELLED! PLEASE ATTEND EITHER MON OR TUE RECITS but do NOT officially drop or add!! | NatSci 210 | |
Recitation R3 | Cuddihy | CS 472: 114814 CS 572: 391068 | M | 2:00 p.m.-2:50 p.m. | NatSci 210 |
Recitation R4 | closed | CS 472: 091816 CS 572: 433832 |
TOPICS:
This course is a survey of artificial intelligence (AI) - the study of how to
program computers
to behave in ways normally attributed to ``intelligence'' when observed
in
humans. (For other definitions, see ``Some
Definitions of Artificial Intelligence''.) Topics will include: the nature of AI, search, logic and
automated reasoning, knowledge representation,
natural-language understanding, and philosophical issues. In addition,
you will learn to use the SNePS semantic-network knowledge-representation
and reasoning system, and you will meet Cassie, a computational cognitive agent
implemented in SNePS.
sunyab.cs.472
or
sunyab.cs.572
. You may post questions and comments there
that are of general interest to the entire class.
From time to time, information about homeworks, etc., will be posted to
the newsgroups.
Tuesday | January 21 | First Lecture |
Mon., Tue., Fri. | January 27, 28, 31 | First meetings of recitations |
Tuesday | February 11 | *** PROJECT 1 (mini-Eliza) DUE *** |
Friday | March 7 | Len Schubert, CS Colloquium speaker |
Tuesday | March 11 | *** MID-TERM EXAM *** (covering some or all of Chs. 1-4, 6-10.2) |
Friday | March 14 | *** Last day to withdraw with a grade of `R' *** |
Sat.-Sun. | March 15-23 | Spring break; no classes |
Tuesday | March 25 | *** PROJECT 2 (automated theorem prover) DUE *** |
Tuesday | April 15 | *** PROJECT 3 (SNePS KB) DUE *** |
Thursday | April 24 | *** PROJECT 4 (NLU) DUE *** |
Monday | April 28 | Roger Schank (Center for Cog. Sci. Distinguished Speaker) |
Mon., Tue., Fri. | April 28, 29 May 2 |
Last meetings of recitations |
Thursday | May 1 | Last Lecture |
Tue., Wed. | May 6, 7 | Reading Days |
Thu.-Fri. | May 8-16 | Exam Week (Assume our exam is the afternoon of the last day) |
Readings | Topics | Lecture Dates |
---|---|---|
R&N 1, 2 Luger 2, 3, 4, 5 | Intro: What is AI? agents, Cassie | Jan. 21-28 |
R&N 3, 4.1, 4.2 Luger 16 |
Search | Jan. 30-Feb. 11 |
R&N 6, 7, 9, 10.1, 10.2 Luger 10, 14 | Logic & automated reasoning | Feb. 13-Mar. 13 |
R&N 8, 10.5, 10.6 SNePS readings Luger 6, 7, 9, 19 | Knowledge Representation | Mar. 25-Apr. 8 |
R&N 22, 23 SNePS readings Luger 8 | Natural-Language Understanding | Apr. 10-Apr. 24 |
R&N 26, 27 Luger 29, 30 | Philosophical Issues | Apr. 29 |
Review | May 1 |
Note to CS 572 students: You may prefer to read the Luger chapters in chronological, rather than topical, order, viz: 2, 14, 3, 16, 19, 7, 8, 9, 4, 10, 6, 5, 29, 30. In any case, there are 14 chapters from Luger, so 1 chapter synopsis will be due on Tuesday of each week.
This is so that the homework can be discussed in the class period when it is due.
acl
), which runs under the Unix operating
system. If you don't have an account on one of the department's or the
university's Unix machines, please get one. (To do this, first get an
account on the CIT ubunix machines; then send mail to
cs-accounts@cse.buffalo.edu
asking for an account on Armstrong for CS
472 or CS 572.) You will be expected to
learn how to use Unix and to learn the idiosyncrasies of Allegro Common
Lisp on your own (the Shapiro text should be of help). For more
information on Lisp, see
``An Introduction to
Common Lisp''.
CIT offers
short courses
on Unix, etc., or call 645-3542, or email
consult@acsu.buffalo.edu
for more information).
The main product of your work is the paper, not the program! In the paper, you should say what you have done, and say (in English summary, not in programming detail) how you have done it. It should also include annotated examples of your program in action. These should be well chosen to illustrate the range of performance of your program. The examples should not be redundant, nor included merely because they look complicated. Each example should illustrate a particular ability of your program. Nevertheless, the reader will assume that your program does nothing interesting that isn't illustrated!
The listing should either be presented as figures throughout the paper, or as an appendix. In either case, the listing is included as documentation for what you say in the paper.
Thus, each report must consist of the following components:
Recitation Assignments (including attendance, homeworks, synopses, quizzes, etc.) | 25% |
Projects | 25% |
Midterm Exam | 25% |
Final Exam | 25% |
Total | 100% |