• October 13th: Project ideas due on Piazza.
• October 20th: Project proposal PDF due on Canvas.
• November 25th and 26th: Progress checkpoint one-to-one meetings.
• December 9th: Project presentations in class.
• December 15th: Project report PDF due on Canvas.

Teams: Final projects can be done either individually, or in teams of 2 students. However, if you choose to work in a team, the scope of your project should justify the need for a team, that is, it should be something that is really hard to pull off with just one person, given the timeline we have for the final projects.

Imaging hardware: Final projects can (and are encouraged) to make use of imaging hardware (cameras, projectors, lights, depth sensors, light field cameras, special lenses, and so on). If you already have access to such equipment, then great! If not, the teaching staff will likely be able to provide it, but you should talk to us in advance.

Each student will post on Piazza up to 3 ideas for a final project. The description of each idea should be short, about one paragraph. The teaching staff will follow up on the posts, with feedback on each idea (whether it is of the right scope for a final project, whether it is too ambitious given the project timeline, and so on). We encourage you to submit the maximum number of ideas, so that you have more options for your eventual project proposal.

Type and scope of final projects: These are intentionally left very open-ended. It could be re-implementing and thoroughly evaluating a published computational photography research paper in scenaria not covered in the paper itself. It could be creating a new computational photography algorithm to produce some visual effect you find interesting. It could be using simple or advanced imaging equipment in some unconventional way. It could be proposing a modification to an existing computational photography system (software, hardware, or both) that you believe could result in some significant improvement. Especially in a field such as computational photography, the possibilities are very diverse and numerous.

Coming up with project ideas: Imagining something exciting and new to do as a project is hard, which is why we have allocated more than three weeks (including the time for your final project proposal) for this. Below are a few pointers that can help you come up with exciting and important ideas. You should also take advantage of office hours between now and the due dates for your ideas and proposal, to discuss potential final project topics with the teaching staff.

• Most lectures (often near their end) include teasers of advanced subjects that relate to the lecture's overall theme. These subjects are not discussed in detail, but the references at the end of the lecture provide pointers to related literature. You can follow up on those pointers.
• If the overall theme of some lecture strongly appealed to you, you can do a literature search to find more recent papers in that area, and peruse those for ideas. Good starting points for your literature search are the related sections in the Szeliski textbook (listed at the end of lecture slides as references), as those almost always discuss key recent advances and papers. Google Scholar is also your friend, especially the option to show citations of a paper, which you can use to search through recent research on topics and papers we discuss in class lectures.
• You can look at final projects from previous offerings of this course, as well as other, related, courses.

Below are some pointers to specific topics that the teaching staff find intriguing and suitable for a final project for this class (most of them make some use of hardware).

• Fun with projectors: direct-global separation, dual photography, optical computing.
• Fun with speckle: seeing through stuff, motion tracking, tampering detection.
• Fun with flashes: flash no-flash pairs, non-photorealistic camera.
• Fun with lightfields: unstructured lightfields, pinhole lightfield camera.
• Fun with apertures and defocus: coded aperture, confocal stereo, extended depth of field.
• Fun with low-budget cameras: imaging with simple lenses, accidental pinholes.
• Fun with image analogies: exemplar-based shape and material.
• Fun with lensless cameras: diffuser cam.
• Fun with phoography: wide-angle portraits, computational zoom, white balancing.

The written project proposal should be a PDF of size between 1-2 pages, to be submitted on Canvas. It should have at least the following sections and content:

• Title. Provide the title of your project and the names of all (up to 2) team members.
• Summary. Summarize your project in no more than 2-3 sentences. Describe what you plan to do and what will be learned.
• Background. Describe in 1-2 paragraphs why this project is hard, useful, and/or interesting.
• Resources. Describe the resources (cameras and other imaging hardware, starter code, dataset, any special computing resources, etc.) you will use. If you are building off of an existing codebase, or an existing hardware setup, please explicitly say so. If there are any books or papers that you are using as references, please provide the citations. Make sure to explain what data (images, videos, etc.) you will use to evaluate your results. If you are doing a hardware project, explicitly mention so and list what equipment you will need. Please also explain whether you already have access to these resources, or whether you would like teaching staff to provide them to you.
• Goals and deliverables. Describe the deliverables or goals of your project. Make sure to separate your goals into what you plan to achieve (that is, the minimum set of goals you believe must be reached for the project to be successful), as well as what you hope to achieve (additional goals you would like to see happen if the project goes really well).
• Schedule. Provide a tentative schedule for your project. List what you plan to get done each week from now until the project due date.
• Team justification. If you are proposing a team project, explain why a team is needed for this project, and why you are the right team for it.

These will be 20-minute one-to-one meetings with each project team. During the meeting, you should be prepared to discuss the status of your project in detail. This includes:

• How much progress you have made towards your goals and deliverables.
• What unforeseen problems you have encountered, how you have addressed them, or how you plan to do so.
• Any differences in the resources you have used or you expect to use before the end of the project, compared to what you described in your project proposal.
• Any adjustments you believe you will need to make to the goals and deliverables you promised in your project proposal.
• How you are doing compared to the tentative schedule you had in your project proposal, and an updated, detailed schedule for the weeks remaining until the end of the project.

The exact meeting schedule will be determined about a week in advance.

There are two final deliverables for your project: A project presentation, and a project report.

Project presentation (December 9th): Project presentations will happen during a special class scheduled during the exam period. Each presentations will last for 5 minutes, with 2 more minutes for questions from the teaching staff and other students. Time limits will be strictly enforced! Therefore, you should make sure to prepare and practice your presentation in advance. You should prepare as many slides you think you need for the 5 minutes you have (we recommend a maximum of 5 slides, or 1 minute per slide).

Project report (December 15th): Your final report should be a PDF of size 4 pages (for 15-463) or 8 pages (for 15-663 and 15-862), plus any additional pages for references. Your report should be written as an ICCP paper, both in terms of content and in terms of formatting (you can use the ICCP author kit for the formatting).

Some of this write-up is inspired from Kayvon Fatahalian's final project instructions for 15-769: Visual Computing Systems.