[Latex Template] [Programming Guidance]

Please carefully read the Academic Integrity before you start working on the homework assignments.

In short, you can get help from the instructors, TAs, textbooks (or relevant books), the Internet, or discussions with your classmates, but you must cite them fully and completely (i.e., provide citations to the book or website link, acknowledge the other students that had discussions with you). Again, you are NOT allowed to:

  • copy anything from the book or the Internet,
  • read or look at anyone else's solutions (write-up or code),
  • share your solutions (write-up or code) with any other students, during or after the completion of the course.

    • When you write down your solution, it MUST be close-book. This is to make sure you truly understand and can recreate the solutions.

    📃 Entrance Exam

    There is an entrance exam for this course. There are 6 programming problems, covering several important algorithms you should have learned in undergraduate algorithm courses (simple sorting and data structures, greedy, DP, graph algorithms). Each of them should only take a few lines of code. You need to finish them in the first week. Each of them is 1 point in your final grade. Ideally you should pass all of them (and get all 6 points). ⚠ I would not recommend anyone getting < 5 points to take the course. If you feel the entrance exam problems are hard, then unfortunately you are not ready to take CS 218 yet. You should consider taking CS 142 this quarter, which will also count toward your graduation requirements.

    📝 Assignments

    There will be in total 5 assignments, each including both written and programming problems (the first programming assignment is the extrance exam). We have 10 deadlines, which is help to push you plan ahead to work on the assignments 😜

    In particular, you need to finish the training programming problems in the first week (except for HW1). Generally they are simpler questions and are not too hard to finish within one week.

    For each assignment, there are 10 basic points, and usually 3-4 bonus points available.

    • About 4-5 points are for the required training programming problems.
    • The other 5-6 points are for the 2 or 3 required written problems.
    • Then, we will have 3 to 4 bonus problems for each assignment, each with 1 point. These are more challenging and advanced problems. They are mostly programming but can be written problems in HW1.
    • The total homework points in the final grade is 44%: each homework (HW1 include entrance exam) is for 11 points, and the highest 4 out of 5 will be counted to your final grade.
    • You can get more than 11 points for each assignment. This also means you can get more than 100 points for your final grade, which will give you an A+. It means you have put tremendous effort in this course! Meanwhile, indeed many of you (usually 20%) can achieve this! You should definitely try!
    • For all the challenge problems, if you finish them before the June 6, you can get half of the points.
    Assignment Release Date Programming Deadline Written Deadline
    HW1 3/28 4/4 (entrance exam) 4/11
    HW2 4/11 4/18 4/25
    HW3 4/25 5/2 5/9
    HW4 5/9 5/16 5/23
    HW5 5/23 5/30 6/5

    🖋 Written Assignments

    You must use LaTeX to prepare your solution. Here you can find sample code for writing solutions using LaTeX.

    In grading, we will reward not only correctness but also clarity and simplicity. To avoid losing points for hard-to-understand solutions, you should make sure your solutions are either self-explanatory or contains good explanations. Please understand that grading your assignments is a lot of work for your TAs and readers, especially determining the correctness and cost bounds for your algorithms. We reserve the right to manually deduct points for solutions that are conceptually correct but does not show a sincere attempt to explain the ideas clearly.

    💻 Programming Assignments

    For all programming assignments, you will submit them on CodeForces. You can find a guidance document here. You still need to submit a short report in your write-up about each of the programming problems. The report does not need to be very long, but should contain:

    • CodeForces id and submission id.
    • A short description of your algorithm.
    • Some analysis of your algorithm (time complexity, correctness, etc.) if needed.

    We run automatic code comparison programs on student solutions. These programs are very good at detecting similarity between code, even code that has been purposefully obfuscated. Such programs can compare a submitted assignment against all other submitted assignments, against all known previous solutions of a problem, etc. The signal-to-noise ratio of such comparisons is usually very distinctive, making it very clear what code is a student’s original creative work and what code is merely transcribed from some other source. Cheating is simply not worth the risk.