CS540, Spring 2019
Department of Computer Sciences
University of Wisconsin–Madison
Course Description: Principles of knowledge-based search techniques, automatic deduction, knowledge representation using predicate logic, machine learning, probabilistic reasoning. Applications in tasks such as problem solving, data mining, game playing, natural language understanding, computer vision, speech recognition, and robotics.
See here or the Canvas website for the tentative syllabus.
(COMP SCI 300 or 367) and (MATH 211, 217, 221, or 275) or graduate or professional standing or declared in the Capstone Certificate in Computer Sciences for Professionals.
The grading for the course will be be based on:
Note: The distribution of CS540 final grades has been as follows. This is an approximation, and changes from semester to semester. The median student's course grade is usually a low B or high BC. The percentiles refer to ranking based on the final weighted score.
All assignments are due at the beginning of class on the due date. One (1) day late, defined as a 24-hour period from the deadline (weekday or weekend), will result in 10% of the total points for the assignment deducted. So, for example, if an 120-point assignment is due on a Wednesday at 8am but it is handed in between Wednesday 8:01am and Thursday 8am, 12 points will be deducted. Two (2) days late, 25% off; three (3) days late, 50% off. No homework can be turned in more than three (3) days late. Written questions and program submission have the same deadline.
In rare circumstances, a student may send the instructor an email and request an extension in handing in the homework. The email MUST detail the justification. The instructor decides whether to grant the extension or not. Under normal circumstances, the total extension in the whole semester cannot exceed two days.
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.