CSCI 446
Artificial Intelligence
Fall 2015

Montana Tech
Computer Science & Software Engineering

Schedule  |  Assignments  |  Course syllabus  |  Moodle

ASSIGNMENTS

This page lists the assignments for the course. When an assignment is released, the assignment column will link to a detailed description of the assignment.

#Due DateTime Assignment
1 Mon. 8/31 11:59pm AIMA Code Base
2 Mon. 9/14 11:59pm Search
3 Fri. 9/25 11:59pm Constraint Satisfaction
4 Mon. 10/12 11:59pm Logical Inference
5 Fri. 10/23 11:59pm Uncertain Reasoning
6 Mon. 11/16 11:59pm Machine Learning
7 Day of Presentation 9:00am AI Topic Paper
8 Mon.-Fri. 11/16-12/4 9:00am Presentation
Project Fri. 12/11 TBD Semester Project

Submission. All assignments need to be submitted via Moodle. In the event of a Moodle failure, email your submission to me before the deadline. You should upload all the source files required by the assignment. You should also include any other files required to run your solution. The top of every source file should include your name, username, and a description of what the file does.

Deadline and late policy. All assignments are due at the stated date and time. Assignments arriving even one minute late are considered late. You get a total of four free late days. Each late day buys you a 24-hour extension to a submission deadline. If you are out of free late days, any further late submissions will be given a zero. Late days do NOT apply to presentations, papers, or exams.

Grading. Your code will be graded on correctness, programming style (including comments), and efficiency. Partial credit is possible so if you run out of time, submit what you have. If you want to do well, start well in advance of the deadline. This allows time to seek help if you run into trouble. Software bugs can be difficult to find and are often easily found after a good night's sleep.

Papers and presentations will be graded using the department's standardized grading criteria: Standardized written assessment and Standardized presentation assessment

Homework grading.

Collaboration policy. Programming is a creative process and no two programmers will solve the same problem in the same way. You are encouraged to discuss how to design a solution to a given problem with your classmates. But when it comes time to convert your design into code, you must write the code yourself. Be sure not to leave copies of your code where others might be able to access it (such as in the recycling bin of a lab computer). You may adapt code from the CSCI 446 course materials and the textbook website provided you cite what code you used in your program's comments.

Under no circumstances should you copy another person's code. Copying code from another student can result in an F in the course. Novices often mistakenly believe simple transformations can disguise a copied program. In actuality, copied programs often reveal themselves quite easily during grading. We can also use sophisticated software such as MOSS to detect plagiarized code.

Page last updated: December 02, 2015