Textbook

Stuart Russell & Peter Norvig, Artificial Intelligence: A Modern Approach,
Prentice-Hall, Third Edition (2009) (required).

Grading

Mini-projects: 50%; Written Assignments: 10%; Final: 30%; Class Participation: 10%.

There will be two mini-projects (that fit together into one large system):

• Mini-project 1: assigned Apr 2nd, due May 2nd noon. Description, Starter Code
  Milestone 1: due Apr 18th 12 pm. DropBox
  Final Report: due May 2nd noon. DropBox
  Best Performing Code
  
• Written Assignment 1: assigned Apr 9th, due Apr 23rd 12 pm. Description, DropBox
  
• Mini-project 2: assigned May 2nd, due May 30th noon. Description, Starter Code and Data
  Milestone 1: due May 16th noon. DropBox
  Final Report: due May 30th noon. DropBox
  Distance matrix for evaluation set (Janara will send you instructions): due May 31th noon. DropBox
  
• Written Assignment 2: assigned May 7th, due May 21st noon. Description DropBox
  

The gradebook can be found here.

Course Administration and Policies

• Subscribe to the course mailing list.
• Mini-projects are to be done individually or in a team of 2. You may discuss the subject matter with other students in the class, but all solutions, code, writeups must be your own. In your writeup mention names of any students (outside your team) with whom you discussed the projects. You are expected to maintain the utmost level of academic integrity in the course.
• Written assignments are to be done individually. You may discuss the subject matter with other students in the class, but all solutions, writeups must be your own. In your writeup mention names of any students with whom you discussed the assignments. You are expected to maintain the utmost level of academic integrity in the course.
• Assignments/Mini-projects may be handed in up to a week late, at a penalty of 10% of the maximum grade per day.
• Comments can be sent to the instructor or TA using this anonymous feedback form

Cheating Vs. Collaborating Guidelines

As referenced from Dan Weld's guidelines.

Collaboration is a very good thing. On the other hand, cheating is considered a very serious offense. Please don't do it! Concern about cheating creates an unpleasant environment for everyone. If you cheat, you risk losing your position as a student in the department and the college. The department's policy on cheating is to report any cases to the college cheating committee. What follows afterwards is not fun.

So how do you draw the line between collaboration and cheating? Here's a reasonable set of ground rules. Failure to understand and follow these rules will constitute cheating, and will be dealt with as per University guidelines.

• The Gilligan's Island Rule: This rule says that you are free to meet with fellow students(s) and discuss assignments with them. Writing on a board or shared piece of paper is acceptable during the meeting; however, you should not take any written (electronic or otherwise) record away from the meeting. This applies when the assignment is supposed to be an individual effort or whenever two teams discuss common problems they are each encountering (inter-group collaboration). After the meeting, engage in a half hour of mind-numbing activity (like watching an episode of Gilligan's Island), before starting to work on the assignment. This will assure that you are able to reconstruct what you learned from the meeting, by yourself, using your own brain.
• The Freedom of Information Rule: To assure that all collaboration is on the level, you must always write the name(s) of your collaborators on your assignment. This applies when two groups collaborate.

Department of Computer Science & Engineering
University of Washington
Box 352350
Seattle, WA  98195-2350
(206) 543-1695 voice, (206) 543-2969 FAX