CS 473: Homework and Exam Policies
The course staff must critically examine several thousand pages of homework and exam submissions this semester! We desperately need your help to make sure your work is graded and returned quickly. If you have any questions or concerns about these policies, please don't hesitate to ask in lecture, during office hours, on Piazza, or by email.
I apologize in advance for the length of this document. Most of this stuff is obvious to almost everybody, but after teaching this class for many years, I've seen a lot of strange things.
All homework solutions must be submitted electronically on the course Moodle site. Submit one PDF file for each numbered homework problem.
Each student must submit individual Homework 0 solutions.
Starting with Homework 1, homework solutions may be submitted by groups of at most three students. We strongly encourage (but will not require) every student to work in a group with at least one other student. Students are are responsible for forming their own homework groups. Groups may be different for each numbered homework problem.
For group solutions, exactly one member of each group should submit the solution to each problem. Even if the groups are identical, the submitter may be different for each numbered homework problem.
Additionally, the submitter must submit all group members' NetIDs in the Online Text box on the Moodle submission page. Separte the NetIDs with single spaces; the order of the NetIDs does not matter. For example:
After we grade the submissions for each problem, we use this information to automatically copy each submitter's grade to the other members of their group. If this information is not entered correctly, the group members' grades will be delayed or possibly lost entirely, including the submitter's.
- If Konstantinos, Patrick, and Yipu are submitting as a group, whoever submits the solution enters "
koiliar2 plin15 ywang298".
- If Konstantinos and Patrick are submitting as a group, whoever submits the solution enters "
- If Patrick is working alone, then Patrick enters "
We will not accept late homework for any reason. To offset this rather draconian policy, we will drop several of your lowest homework problem scores; see the grading policies for more details.
In extreme circumstances, we may forgive quizzes, homeworks, or even exams. Extreme circumstances include documented illness or injury, but do not include registering late, travel for job interviews or conferences, forgetting the homework deadline, or just not finishing on time. We will compute your final course grade as if your forgiven homeworks and exams simply do not exist; your other work will have more weight. Please ask Jeff for details.
To keep grading fast and consistent, each numbered homework problem will be graded by a single person, and we will record grades for each problem separately. We need your help to make distribution of problems to graders possible.
All homework submissions must be in PDF format (not plain text, Word, or HTML).
We strongly recommend typesetting your homework solutions using LaTeX. (In particular, we recommend TeXShop for Mac OS X, TeX Live for Linux (already included in most distributions), and MiKTeX for Windows.) We will provide a LaTeX template for homework solutions.
If you must submit scanned handwritten solutions, please follow these guidelines:
- Write your solutions on plain white printer paper (not notebook or graph paper).
- Write your solutions using black ink (not pencil).
- Write clearly, neatly, and slowly. If you make a small mistake, scratch it out. If you make a big mistake, start over.
- Use a professional scanner (not a phone camera).
- Print your PDF file on a black and white printer before submission to ensure readability.
Please include the names and NetIDs of all group members on the first page of each solution. Yes, in addition to entering the NetIDs on the Moodle submission page. Given the size of the class, we need some redundancy.
Form: How to write
Please make it easy for the graders to figure out what you mean in the short time they have to grade your solution. A portion of every homework grade is specifically devoted to clarity and style.
If your solutions are difficult to read or understand, you will lose points.
- Write everything in your own words, and properly cite every outside source you use. We strongly encourge you to use any outside source at your disposal, provided you use your sources properly and give them proper credit. If you get an idea from an outside source, citing that source will not lower your grade. Failing to properly cite an outside source—thereby taking credit for ideas that are not your own—is plagiarism.
The only sources that you are not required to cite are the official course materials (lectures, lecture notes, homework and exam solutions from this semester) and sources for prerequisite material (which we assume you already know by heart).
- List everyone you worked with on each homework problem. Again, we strongly encourage you to work together, but you must give everyone proper credit. If you work in a group of 20 students, then all 20 names should appear on your homework solution. If someone was particularly helpful, describe their contribution. Be generous; if you're not sure whether someone should be included in your list of collaborators, include them. For discussions in class, in section, or in office hours, where collecting names is impractical, it's okay to write something like "discussions in class".
Please see our academic integrity policy for more details.
If we can't decipher your solution, we can't give you credit. If you have sloppy handwriting, use LaTeX. Please don't submit your first draft. Writing legibly also helps you think more clearly.
You will lose points for poor spelling, grammar, punctuation, arithmetic, algebra, logic, and so on. This rule is especially important for students whose first language is not English. Writing sensibly also helps you think sensibly.
We can only grade what you actually write, not what you mean. We will not attempt to read your mind. If your answer is ambiguous, we will deliberately choose the interpretation that makes it wrong. Writing carefully also helps you think carefully.
Avoid the Three Deadly Sins. Yes, we are completely serious about these. We reserve the right to add more Deadly Sins later in the course.
- Write solutions, not examples.
Don't describe algorithms by showing the first two or three iterations and then writing "and so on". Similarly, don't try to prove something by demonstrating it for a few small examples and then writing “do the same thing for all n”. Any solution that includes phrases like “and so on”, “etc.”, “do this for all n”, or “repeat this process” automatically gets a score of zero. Those phrases indicate precisely where you should have used iteration, recursion, or induction but didn’t.
Declare all your variables. In English.
Whenever you use a new variable or non-standard symbol for the first time, you must specify both its type and its meaning. Similarly, when you describe any algorithm, you must first describe in English precisely what the algorithm is supposed to do. Any solution that contains undeclared variables automatically gets a score of zero, unless it is otherwise perfect.
Never use weak induction. Always, always, always use a strong induction hypothesis, even in proofs that only apply the induction hypothesis at n-1. Why would you even want to tie n-2 hands behind your back? Any proof that uses a weak induction hypothesis automatically gets a score of zero, unless it is otherwise perfect. Basically, weak induction should die in a fire.
- State your assumptions.
If a problem statement is ambiguous, explicitly state any additional assumptions that your solution requires. (Please also ask for clarification in class, in office hours, or on Piazza!) For example, if the performance of your algorithm depends on how the input is represented, tell us exactly what representation you require.
- Don't submit code.
Describe your algorithms using clean, human-readable pseudocode. Your description should allow a bright student in CS 225 to easily implement your algorithm in their favorite language.
- Don't submit your first draft.
Revise, revise, revise. After you figure out the solution, then think about the right way to present it, and only then start writing what you plan to submit. Yes, even on exams; do your initial scratch work on the back of the page.
- Keep it short. Every homework problem can be answered completely in at most two typeset pages or five handwritten pages; most problems require considerably less. Yes, I am aware of the crushing irony.
- Omit irrelevant details. Don't write "red-black tree" when you mean "balanced binary tree" or "dictionary". Don't submit code; We want to see your ideas, not syntactic sugar.
Don't regurgitate. Don't explain binary search; just write "binary search". Don't write the pseudocode for Dijkstra's algorithm; just write "Disjktra's algorithm". If the solution appears on page 6 of Jeff's notes, just write "See page 6 of Jeff's notes." If your answer is similar to something we've seen in class, just say so and (carefully!) describe your changes. You will lose points for vomiting.
Don't bullshit. If you don't know the answer, just say so. Answering “I don't know” (and nothing else) is worth 25% partial credit. The "I don't know" rule applies to every required problem and sub-problem on every homework and exam, but not to extra credit problems. Synonyms like “No idea” or “Je ne sais pas” or "WTF" are acceptable substitutes, but you must write something; a blank page is worth zero points. Readable, correct, but suboptimal solutions are always worth more than 25%.
Content: What to write
- Answer the right question. No matter how clear and polished your solution is, it's worthless if it doesn't answer the question we asked. Make sure you understand the question before you start thinking about how to answer it. If something is unclear, ask for clarification! This is especially important on exams.
- Justify your answers. Unless the problem specifically says otherwise, every homework problem requires a proof. Without a proof, even a perfectly correct solution is worth nothing. In particular, the sentence "It's obvious!" is not a proof—'obvious' is often a synonym for 'false'! However, proofs are only required on exams if we specifically ask for them.
By default, if a homework or exam problem asks you to describe an algorithm, you need to do several things to get full credit:
Some problems may deviate from these default requirements. For example, we may ask you for an algorithm that uses a particular approach, even though another approach may be more efficient. (Answer the right question!)
- If necessary, formally restate the problem in terms of combinatorial objects such as sets, sequences, lists, graphs, or trees. In other words, tell us what the problem is really asking for. This is often the hardest part of designing an algorithm.
- Give a concise pseudocode description of your algorithm. Don't regurgitate, and don't turn in code!
- Describe a correct algorithm.
- Justify the correctness of your algorithm. You usually won't have to do this on exams.
- Analyze your algorithm's running time. This may be as simple as saying "There are two nested loops from 1 to n, so the running time is O(n²)." Or it may require setting up and solving a summation and/or a recurrence, in which case you'll also have to prove your answer is correct.
- Describe the fastest correct algorithm you can, even if the problem does not include the words "fast" or "efficient". Faster algorithms are worth more points; brute force is usually not worth much. We will not always tell you what time bound to shoot for; that's part of what you're trying to learn. However, if your algorithm is incorrect, you won't get any points, no matter how fast it is!