The following table indicates assignments and due dates for Computer
Science 261. Unless otherwise indicated,
textbook references are to Thomas Dean, James Allen, and Yiannis Aloimonos,
Artificial Intelligence: Theory and Practice, Benjamin/Cummings
Publishing Company, Inc., 1995;
written assignments may be done collaboratively;
programming assignments and projects are to be done individually --
collaboration is not allowed.
|Due Date ||Chapter ||Collaboration? ||Problems |
|Wed., Jan. 28 ||2 ||No ||2.3, 2.4 |
|Fri., Feb. 6 ||3 ||Yes ||3.2, 3.7 |
|Wed., Feb. 11 ||Resolution Handout || Yes ||3, 4 |
|Mon., Feb. 16 ||Resolution Handout || Yes ||5, 6, 7 |
|Mon., Mar. 2 ||
Project on Proof|| No || Draft Version |
|Wed., Mar. 4 ||
Project on Proof|| No || Final Version |
|Fri., April 24||
Project on Physical Training|| Yes|| Group Preliminaries |
|Mon., May 4 ||
Project on Physical Training|| No|| Rule-based System |
| || |
| || || || |
Submitting Programs For This Course:
In turning in any programs for the course, please follow these directions:
The first three lines of any LISP program should be comments containing
your name, your mailbox number, and an identification of assignment being
solved. For example:
;;; Henry M. Walker
;;; Box Y-06
;;; Assignment for Wednesday, January 28
Also, a comment is needed for every procedure, stating in English what that
procedure is supposed to do.
Obtain a listing of your program and a record of relevant test runs using the
Within a dtterm window (before running LISP), begin
recording session with the statement
where filename is the name of the file in which you want the session
Print a copy of your LISP definitions with the command
where LISP-file.ss is the name of the file containing
your LISP program. If your work involves several files, list all of them
with the cat command.
Run LISP as usual, with the acl command.
Load file LISP-file.ss with the load command.
Run appropriate test cases to check the correctness of your program.
Stop LISP with <Ctrl/D> as before.
Stop recording by typing <Ctrl/D> one more time.
- Print the record of your session by typing
Either write on your printout or include a separate statement that argues
why your program is correct, based upon the evidence from your test runs.
This document is available on the World Wide Web as
created January 4, 1998
last revised April 19, 1998