6.819/6.869: Advances in Computer Vision

Spring 2021

[Home | Policy | Schedule | Course Materials | Final Project | Piazza | Canvas ]

Project Topics

Final Project is an opportunity for you to apply what you have learned in class to a problem of your interest in computer vision. We recommend you work in teams. Each team can be up to 2 people.

The first step will be to propose a project. We have two options for you below. If you pick option 1 (going with a suggested topic), then your project proposal only needs to let us know which topic you picked. If you go with option 2 (your own idea for a project), then you will need to write a short doc proposing what you will do (details below under the Option 2 secton).

Proposal due: Mon April 12. Upload to Canvas.

Option 1: Choose from the suggested topics.

You could choose from the list of suggested topics:

Option 2: Your own project.

​ You could select a topic in computer vision that interests you most and work on it as your course project. Potential projects could be based on applications and models: Please clearly specify and justify: (1) what will be the approach; (2) why is it interesting; (3) how will you evaluate success. You could take a look at the Resources (image datasets and papers) in the Course Materials for some inspiration. Before proceeding this option, please find teammates through Piazza then draft a summary of the project proposal together and submit it as your project proposal on Canvas, then (optionally) set up a meeting about the project detail. ​ ​

Forming Groups

The rules for forming groups are:
  1. 6.819 and 6.869 students can mix up and form a team; these teams will be evaluated by 6.869 standards. Please specify 6.819 or 6.869 for each team member in the report.
  2. Groups can have up to 2 members.
  3. Reports should be individually submitted and it should highlight the contributions of each team member on a section of the paper.


The report should be about 3n pages for 6.819, and 4.5n pages for 6.869, including references, where n is the number of team members (that is, two person projects should be about twice the amount of work and content as one person projects). The report should be in CVPR format. It should be structured like a research paper, with sections for Introduction, related work, the approach/algorithm, experimental results, conclusions and references. We expect at least 30 hours of work per team member on the project, and we are allocating time in the schedule to accomodate this (the workload will be consistent with problem set expectations during the equivalent time period). Project reports should be individually submitted and the contributions of each team member should be clearly described.

Regarding the reports:

You should describe and evaluate what you did in your project, which may not necessarily be what you hoped to do originally. A small result described and evaluated well will earn more credit than an ambitious result where no aspect was done well. Be accurate in describing the problem you tried to solve. Explain in detail your approach, and specify any simplifications or assumptions you have taken. Also demonstrate the limitations of your approach. When doesn’t it work? Why? What steps would you have taken have you continued working on it? Make sure to add references to all related work you reviewed or used.

You are allowed to submit any supplementary material that you think it important to evaluate your work, however we do not guarantee that we will review all of that material, and you should not assume that. The report should be self-contained.

Submission: submit your report to canvas as a pdf file named <your_kerberos>.pdf. Submit any supplementary material as a single zip file named <your_kerberos>.zip. Add a README file describing the supplemental content.

​ ​

Grading Policy

Final project occupies 40% of the course grade. The following is the weight for two parts: