-
Notifications
You must be signed in to change notification settings - Fork 39
Organization
This course consists of lectures, reading and reviewing research papers, and a final project.
- Paper reviews: 45%
- 9 papers, 5% each
- Final Project: 50%
- Team formed by deadline: 5%
- 1-page project proposal: 15%
- Project presentation: 15%
- Final report: 15%
- Class Participation: 5%
Most work in this class consists of reading research papers. We will cover one paper per week. For each paper, you are required to write a review.
A review should start with a short, neutral summary of the paper (1-2 paragraphs), followed by a list of paper's main contributions/insights, and a list of its limitations. Finally, answer specific questions posted for this paper on the Reading List (if any). Our goal is to get you to think deeply and critically about the paper, not to test you. You won’t be graded on the correctness of your reviews; any non-trivial review will get you 5%.
The reviews are due every Wednesday by the end of the day. Reviews are submitted via Google Forms. Links to papers and forms, as well as questions you have to answer in your review will be posted in the Reading List at least one week before the review due date.
The goal of the project is to gain an in-depth understanding of the techniques presented in the course by re-implementing them, applying them to a new domain, or extending them. A list of possible project topics is available here. You can also suggest your own project, pending instructor approval. If you are already working on a research project that fits the theme of this course, feel free to use this as your final project (but please let us know). If you are taking another 291, feel free to propose a single cross-project for both courses.
Projects are expected to be done in teams of two or three. The scope of the project should be commensurate with the size of the team and whether this is a cross-project for multiple courses.
There will be four milestones throughout the quarter:
- By the first milestone, form and register your team.
- The second milestone is a project proposal where you explain what you plan to do and why you think it’s a good idea. This is a one-page document (PDF or GoogleDoc). The proposal should include a concrete example, illustrating (a) what is the input to your synthesizer (b) what is the output of your synthesizer, and (c) how does the algorithm roughly work to get from this input to this output.
- The third milestone is a short presentation describing your project; the exact length of the presentations will depend on the number of projects that are submitted.
- At the end of the quarter, you are expected to submit a final report describing your project. The report should be 3-8 pages in length in the PACM PL format (follow formatting requirements from this call for papers). The report should read like a short paper, so it should make it clear what you did, why you did it, and what you learned from doing it.
Overall, projects will be judged in terms of quality of execution, originality and scope.
To earn class participation points, you should participate in discussion during the lecture or on the canvas discussion board.