|
Homework 1: pdf,
code, solution, solution code. Due Tues, Jan 25 in Class.
Homework 2: pdf,
data, solution, solution code. Due Fri, Feb 4 at 4pm, in Sharon Cavlovich's office (GHC 8215).
Homework 3: pdf,
data, solution, solution code. Due Thurs, Feb 17 Tues, Feb 22 in class.
Homework 4: pdf, solution. Due Tuesday, March 1 in class.
Homework 5: pdf, solution. Due Tuesday, April 19 in class.
Homework 6: pdf, solution. No collection, no grading.
|
|
Note - We might reuse problem set questions from previous years, covered by papers and webpages, we expect the students not to copy, refer to, or look at the solutions in preparing their answers. Since this is a graduate class, we expect students to want to learn and not google for answers.
|
Collaboration policy - Homeworks must be done individually, except where otherwise noted in the assignments. 'Individually' means each student must hand in their own answers, and each student must write their own code in the programming part of the assignment. It is acceptable, however, for students to collaborate in figuring out answers and helping each other solve the problems. We will be assuming that, as participants in a graduate course, you will be taking the responsibility to make sure you personally understand the solution to any work arising from such a collaboration.
|
Late homework policy -
- Late homeworks will be penalized according to the following policy:
- Homework is worth full credit at the beginning of class on the due date.
- It is worth half credit for the next 48 hours.
- It is worth zero credit after that.
- Turn in hardcopies of all late homework assignments to Sharon Cavlovich.
Put down the date and time of submission on the HW sheets when submitting your assignments to Sharon. If she is not available, please slide your HW under her door.
- Don't forget that your lowest homework score will be dropped from your final grade.
|
|
