Introduction to Artificial Intelligence

CS540, Spring 2019
Department of Computer Sciences
University of Wisconsin–Madison

Homework

Problem sets will consist of both written exercises and programming problems. There will be about 10 assignments. Solutions are usually submitted on Canvas, but check individual homework assignments for submission instructions. To get a sense about the homework assignments, please check the websites of past semesters for examples.

Exam

  • Midterm Exam: Mar 14. General session: 5:30pm-7:00pm, Ingraham B10;
    McBurney session: 5:30pm-8:30pm, Social Science 4322;
    Makeup session: March 8, 5:30pm-7pm, CS 1240.
    Topics covered: all topics in lectures up to the exam; related slides and notes.
  • Final Exam: May 7. General session: 10:05AM - 12:05PM, VAN VLECK B102;
    McBurney session: 11:00AM - 2:00PM, CS 7331.
    Topics:
         everything on the course webpage, including slides, notes, selected readings (but not whole books, not the optional readings)
         logic: resolution in propositional logic, and English to FOL translation (but not other inference techniques)
         neural network and reinforcement learning topics limited to what's covered in class (but LeNet-5 in neural networks and Q-learning are not required)

All exams are closed book. Bring a calculator and copious amount of blank scratch paper. One 8.5x11 sheet of paper with notes on both sides allowed (handwritten or typed). Lectures and readings on the syllabus page are required, with a few exceptions (e.g., the optional readings). You are responsible for topics covered in lecture even if there are no lecture notes on the topic. You should have knowledge sufficient to work through simple examples. Exam grading questions must be raised with the instructor within one week after it is returned.

Academic Integrity

All examinations, programming assignments, and written homeworks must be done individually. Cheating and plagiarism will be dealt with in accordance with University procedures (see the UW-Madison Academic Misconduct Rules and Procedures). Hence, for example, code for programming assignments must not be developed in groups, nor should code be shared. You are encouraged to discuss with your peers, the TA or the instructors ideas, approaches and techniques broadly, but not at a level of detail where specific implementation issues are described by anyone. If you have any questions on this, ask the instructor before you act.

Exam Archives

Note the exam format, scope and order of topics might be different.