Faculty of Science Home Page University of Alberta Home Page

CMPUT 366 Schedule

See Syllabus

Please fill out this questionnaire.

Assignment Description

This is still tentative!
         Topic  % of course
[total marks]
 
Due date Grader
1 Agents, Search
[state space representations, heuristic evaluation functions, constraint satisfaction, GSAT, Games]
DIMACS site
 18 [120] 5 Oct 06
(start of class)
chonghai
2 Logic, representation, planning
[Entailment, Propositional logic, Predicate calculus, Resolution, ...] (Sudoku Datasets)
 18
[150]
31 Oct 06
(start of class)
#1-6: jma
#7: susan
3 Bayesian reasoning, Decision Nets, etc [Sequential Game (Theory), ...]  18 [110] 23 Nov 06
(start of class)
#3,5: susan
#1,2,4,6: chonghai
4 Sequential Decision Processes (MDP), Learning  12 [115] 8 Dec 06
11:59pm
jma
FINAL Previous Final Examples
Study Guide (tentative outline)
 34 [100] 12 Dec
2-5pm

 

Scores: Gradebook   (Login = CNS account; password = student id)

General comments on the assignments:

Please read these carefully. Not following these overall guidelines may result in point penalty for the assignment.

  • Many assignments will includes both written questions and coding questions. Here, your submission should contain two parts: (1) A hard-copy part with your answers to the written questions and a high-level description of each of the coding questions. (2) The code itself, which must be submitted using ASTEP, before the time specified in the assignment. For more information about ASTEP, see here.
  • For the written questions:
    • Make sure your name is clearly printed on your hardcopy submission. For the sake of your privacy, do not include your student ID.
    • if you hand-write, instead of type, the written part of your assignment, you must make sure that your writing is legible.
    • you should be clear and concise ('more' does not imply 'better') and explain your answers.
    • prominently display the question number and letter.
  • For the coding questions:
    • It is up to you to convince the grader that your code works; not vice versa. This means you should include documentation, describing what the code does, and how it should work. It should also include traces that illustrate this behaviour.
    • You should follow standard 'good' coding practices: meaningful names, proper indentation, appropriate comments, etc.
    • Use the exact command-line arguments (if any), directory names and file names as described in the assignment specification so that we can run scripts to compile and test your programs automatically.
    • In general, the question will specify the language for your code (which will typically be C or C++).
    • Each coding question should be done in its own subdirectory. Typing 'make' in the subdirectory should compile the program. The name of the executable should be the same as the name of the subdirectory.

Labs:

In general, the labs are basically a designated time to see the TA's. This why the TAs are only there just before HWs are due. (We may have some additional labs to introduce other material. But if so, we will announce these auxiliary labs well in advance.)