Homework Information
CMPS 122 (Spring 2004)
There will be 4–6 homeworks in class. They are not optional, and will be graded. You need not do every homework, but missing homework counts as a 0.
| Homework | Assigned | Due | Solutions |
|---|---|---|---|
| HW 1 | April 2 | Friday, April 9th at 10 AM | HW 1 solutions |
| HW 2 | April 12 | Monday, April 19th at 10 AM | HW 2 solutions |
| HW 3 | April 26 | Tuesday, May 4th at 11:59 PM | HW 3 solutions |
| HW 4 | May 17 | Monday, May 24th at 11:59 PM | HW 4 solutions |
| HW 5 | May 24 | Wednesday, June 2nd at 11:59 PM | HW 5 solutions |
Access to the above solutions is restricted when you're off-campus.
Doing homework
You may use any programming languages and any tools you like to do the homework problems, except when the problem specifically says you can't do this. If you use tools you got from the Web or elsewhere, you must cite your sources in your solutions.
All work must be your own. This means that you can't ask someone else "where did you get that cool tool?" You may, of course, do the Google search yourself, but finding the appropriate tool is part of the problem. You're encouraged to visit either the professor's or the TA's office hours if you'd like help with the homework—please visit soon after the homework is assigned to ensure maximum time to get help with the assignment.
Turning in homework
Homework must be turned in using submit on unix.ic; the class name for this class is cmps122-elm.s04. Acceptable formats are plain (ASCII) text and Adobe Portable Document Format (PDF); other formats will not be accepted. Your solutions should be called either hw1.txt or hw1.pdf, as appropriate. Your name and CATS account must appear at the top of your solutions.
If the assignment requires you to turn in any source code, the code should be turned in separately. Code submissions should include a Makefile, and the solution you turn in for that problem should describe how to build and run any code you might need. If you wrote your own code for the assignment, but you didn't need to (for example, you could have downloaded the tool from the Web), you can either hand the code in separately or include it in your solutions. We won't run your code unless the problem explicitly asks you to write it.
Challenge problems
In addition to regular problems, there are "challenge problems" that are entirely optional. These problems are often quite difficult, and may not have a solution. Each challenge problem listed below has a point value; if you provide a complete and correct solution to the problem, these points are divided by 10 and added to your final grade. You may work in teams on challenge problems; see the syllabus for details on how points are assigned if you do so.
Last updated 19 May 2004 by Ethan L. Miller (elm at ucsc d0t edu)
