CS540-2: Introduction to Artificial Intelligence
Spring 2014 Homeworks 

Homework Assignments: 


Homework 1: Due Wednesday, February 12, 11:59pm : pdf code solutions
Homework 2: Due Friday, February 28, 11:59pm : pdf code solutions
Instructions for using the Checkers Framework with Eclipse
Class tournament
There will be a class tournament using the "competitive player" you write.
It will be run by the TA after the due date. Each entrant will play every other
entrant twice, once going first (red) and once going second (black). A win is
worth 3 points, a tie 1 point, and a loss 0 points. Extra credit points will be
given to the top players in the tournament. The tournament will use approximately
100 ms/move and 30-45 seconds as a threshold to determine draws.
Links on Checkers
Rules for playing Checkers
Play Chinook Checkers program
A Samuel's famous paper Some studies in machine learning using the game
of checkers. II - Recent progress, IBM Research Journal 11(6), 1967, 601-618.
A neural network for playing Checkers
An online version of Minesweeper that uses CSP
Some games that are especially hard for computers to play well
Arimaa
Go
Try playing Go yourself
Homework 3: Due Wednesday, April 2, 11:59pm : pdf code solutions
Homework 4: Due Friday, April 18, 11:59pm : pdf code solutions (original dataset (UCI ML Repository), car dataset for pruning

Homework 5: Due Monday, May 5, 11:59pm : pdf code solutions
Naive Bayes classifier description (Wikipedia)
Better Bayesian Filtering by P. Graham on using Naive Bayes for spam filtering 
Boosting and Naive Bayesian Learning paper by C. Elkan for use in Extra Credit problem 


Submit code and keep track of your grades through the Moodle system.

Homework assignments will include written problems and programming in Java.
Accounts will be provided on the Computer Sciences Department's instructional
Unix workstations located in rooms 1350, 1351, and 1370.  Frequently-asked 
questions (FAQs) on homework assignments will be e-mailed to the class mailing list.  
Assignment grading questions must be raised with the instructor within one week after it is returned.

How to Hand In Your Homework: 
For each homework, hand in a pdf copy of any written parts.
Be sure to follow this naming convention when nameing your files: 

<lastname>.<firstname>.HW<#>.P<#>.pdf
replacing lastname, firstname, HW number and Problem number with appropriate values.

If there is a programming part, electronically hand in files containing the Java
code that you wrote for the assignment. You should not hand in any ".class" files.  
(Instructions on how to hand in code will be given for each homework ...)

Useful Tips: 
CS Department Computer Systems Lab (CSL)
CS Department Policy on Student Instructional Computer Accounts
FAQs on almost everything
Unix/Linux 
CSL's Linux Orientation
 
Java
Java On Computer Systems Lab Workstations
The Java Tutorials (Sun)
Introduction to Programming Using Java by David J. Eck
Brewing Java: A Tutorial by Elliotte Rusty Harold
If java is reporting "stack overflow" errors, your code may be correct,
 but very recursive (so don't be surprised).  Try adding the following line in 
your .cshrc.local file:  alias java 'java -oss2000m'
Printing
Printing on CS printers
A useful command for readably printing your source code is:  enscript -2rGE [file]

Late Penalties: 
All assignments are due at 11:59pm 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 
assignment is due on a Wednesday and it is handed in between Wednesday 12:00 a.m. and 
Thursday 12:00 a.m., a 10% penalty 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.  A total of three (3) 
free late days may be used throughout the semester without penalty.  You must specify
on the first page of your late homework how many free late days to use.

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.

[Back to CS540 homepage]