Class participation: 20%
Topic presentation (quality, clarity, depth, etc.): 30%
Course project: 50%

  • Progress Report: 10%

  • Final Report: 30 %

  • Presentation: 10 %

We will use Gradescope. Please use the access code “94PP8P”.

For related questions to the course, please use Piazza.

Paper Presentation (Group)

Each lecture has a theme. The first half of the lecture will be an instructor lecture, and the second half will be a student presentation on the same topic. We will assign groups of three or four for each topic. Although we will provide a sample of literature on the topic, you are expected to present a holistic overview of the topic; this is not a paper presentation. Your presentation should include:

  • Introduction: introduce the topic, give a brief overview of what it is and explain why it is important. Briefly outline the technical aspects of major results in the area.

  • Relationship to previous topics: indicate its relationship to topics we've previously covered.

  • Review of previous work: this is an important section; make sure that an appropriate background is given. Don't hesitate to review previous/preliminary concepts that are critical for the understanding of the presented work. If a good background is given, it is easier to explain the details of the method and technical solution later on.

  • Technical part: Summary of the technical solutions, followed by the details of the technical solutions. Prioritize where necessary. Discuss the similarities/differences of works within the area when appropriate. If relevant, attempt to show how individual works build upon other works in the area. Make sure to cite papers on slides when describing a work.

  • Results: If applicablle, present experimental results from different methods with plots, graphs, images and visualizations.

  • Conclusions: what's the take home message?


  • Please meet with a CA or instructor no later than ten days before your presentation so that we can clarify the topics and varify that you understand the requirements.

  • Early in the week before your presentation (Monday or Tudsday) you must arrange to meet with a CA or instructor. Have an outline of presentation material ready.

  • When slides are ready (but before the weekend), you must arrange to meet with one of us again prior to presenting to get initial presentation feedback.


  • Presentation slides must be made in Google Slides using this template.

  • Slides are due the Saturday before your presntation at midnight. You must send the link to Amir via email at this time.

  • Next, upload your slides to Gradescope


  • The presentation needs to be about 30 minutes long, with an additional 10 minutes of questions + discussion from the class.


  • The presentation will be evaluated based on how comprehensive and correct the portrayed landscape of the topic was, the clarity of the presentation, quality of the slides, how well you get your message across, and how well you handle the questions at the end. Remember that this is not intended to be a paper presentation, but to prepare you for giving a lecture/invited talk.

Project Progress and Final Report (1-3 Students; 2 Recommended)

To see the list of projects completed by our students this year, please see Prior Projects.

Use the CVPR LaTeX template.

Max 6 pages for progress and 10 pages for final report.

Title and authors

Abstract: short summary of the project with main results

6 sections:

  1. Introduction: introduce the problem you want to solve, explain why it is important to solve it; and indicate the method you used to solve it. add a concept figure showing the overall idea behind the method you are presenting.

  2. Previous Work

    1. Review of previous work (i.e. previous methods that have explored a similar problem)

    2. Say why your method is better than previous work; and/or summarize the key main contributions of your work;

  3. Technical Part

    1. Summary of the technical solution

    2. Details of the technical solution; you may want to decompose this section into several subsections; add figures to help your explanation.

  4. Experiments: present here experimental results of the method you have implemented with plots, graphs, images and visualizations.

  5. Conclusions: what's the take home message?

  6. References (counts towards page limit)


  • Your project report will be evaluated based on the quality of the writing, the clarity of your technical explanation and, overall, how well you get your message across. If you follow the structure above, you'll have good chances to do a good job.

Project Source Code:

  • There is no need to attach a print out of the source codes to the manuscript. Final source codes of your working program need to be collected into a unique (zipped) file; this file is due on the project submission deadline date and it is supposed to be sent to the course staff email.

Class participation

  • We take attendance and expect the students to actively engage in the class.
  • If you have a justified reason for not being able to attend a class, e.g. traveling to a conference, please inform us beforehand. We grant exceptions only under justifiable circumstances and on a case-by-case basis.

Late Day Policy

  • We give you up to three (24hr) late days that can be used for the proposal, progress report, and the final report. You are free to distribute them among the three assignments in any way you choose. However, we will not accept late submissions outside of the three late days.
  • When using a late day, please clearly indicate that you are using a late day by writing it on the cover sheet of your pdf submission.