CSE logo University of Washington Computer Science & Engineering
 CSE 473: Artificial Intelligence I
  CSE Home   About Us    Search    Contact Info 

Administration
 Syllabus
 Email Archive
 Schedule as RSS
   

Welcome to CSE 473 for Spring 2004!

Time Schedule:

MWF 1:30-2:20 MOR 234

Instructor:

Oren Etzioni
etzioni@cs.washington.edu
Allen Center 580

Teaching Assistant:

Brian Ferris
bdferris@cs.washington.edu
Allen Center 394
Office Hours: 3:30-5 on Wed in CSE220 and 10:30-12 on Thurs in CSE 218
 

Syllabus:

As PDF or Post Script. I will also attempt to keep up an RSS feed with all lectures and assignments: Schedule .

Mailing List:

Please visit http://mailman.cs.washington.edu/mailman/listinfo/cse473 to subscribe to the class mailing list.

Lectures:

  1. Introduction [ PPT | PDF ]
  2. Search [ PPT | PDF ]
  3. Informed Search [ PPT | PDF ]
  4. CSP [ PPT | PDF ]
  5. More CSP [ PDF ]
  6. Yet Even More CSP [ PDF ]
  7. Game Theory [ PS | PDF ]
  8. Logic Agents [ PS | PDF ]
  9. First-Order Logic[ PS | PDF ]
  10. Planning [ PS | PDF ]
  11. Talking to Your Toaster [ PPT | PDF ]
  12. Computational Evolution [ PPT | PDF ]
  13. Machine Learning [ PPT | PDF ]
  14. Ensemble Learning [ PPT ]
  15. Decision Trees [ PPT | PDF ]

Assignments:

Problem sets will be handed out on Fridays and are due at the beginning of class one week later. The TA will hand problem sets back one week after they turned in.

Important Details

Grading and Late Work

As stated in the syllabus, late problem sets will receive zero credit.

Your grade in the course will be determined as follows:

  • 50% problem sets
  • 25% midterm
  • 25% final

You can drop your lowest problem set score.

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.

CSE logo Computer Science & Engineering
University of Washington
Box 352350
Seattle, WA  98195-2350
(206) 543-1695 voice, (206) 543-2969 FAX
[comments to bdferris]