Course information

Time and location: MWF 11:30 - 12:20 pm in ZACH 350
Office hours: MW 2:00 - 3:00 pm
Office location: 406 PETR
Email: nimak@tamu.edu
Campuswire: link in the syllabus

TA: Pedro Figueiredo
Email: pedrofigueiredo@tamu.edu
Office hours: TF 2:00 - 4:00 pm
Location: Peterson 402

Overview

Computational photography is a collection of computational algorithms and system designs (e.g., sensors, optics) to avoid the limitations of standard cameras and enable novel applications. In recent years, there has been increasing interest in computational photography because of the widespread use of the cameras by the general public through smartphones and other cheap imaging devices. In this course, we first discuss the cameras and the image formation process. We then study basic image and video processing tools like sampling, filtering, and pyramids. Finally, we discuss several image-based algorithms, such as image retargeting, high dynamic range imaging, and texture synthesis.

Prerequisites

Undergraduate: (CSCE 315 or CSCE 331) and (MATH 304 or MATH 311)
Graduate: Graduate students are expected to have similar background.

Textbook

The primary reference of the course is the following book, which covers most of the topics related to computational photography:

Computer Vision: Algorithms and Applications, by Richard Szeliski, 2010

Grading

• Programming assignments (65%): There will be 6 programming assignments for this course. All the assignments are going to be in Python.
  - Undergraduate: The students need to complete the 6 programming assignments.
  - Graduate: In addition to the 6 programming assignments, the graduate students need to complete extra parts for some of the assignments, which are specifically designed for them.
• Midterm Exam (15%): There would be a midterm exam on March 27th during class.
• Final project (20%): Students are free to choose any project related to computational photography. They can work individually or in teams of up to 3 students. The team members should all be either graduate or undergraduate students (mixing is not allowed). Students will propose the project at the middle of the semester. The final project report will be due on May 5^th.

Late Submissions

You will lose 20% from each assignment for each day that it is late. However, there will be 5 granted late days for the entire course. You are free to use it for any of the assignments (note that, you CANNOT use it for the final project!). You will not get any bonuses for any of the unused late days. All the assignments are due at 11:59 pm on Canvas unless otherwise stated. Note that, one minute over and 23 hours over both count as one full day.

Academic Integrity

The assignments in this class are individual unless otherwise stated. For the individual assignments, all the codes need to be written by the student. If indicated in the assignment’s instruction, the use of external libraries for performing basic operations is allowed. However, using an outside source code is NOT permitted. Moreover, collaborating with other students on assignments beyond general discussions is NOT allowed. In general, looking at other students’ code and/or written answers is NOT allowed. If the students have any questions regarding this issue, they should contact the instructor. The students should not post their code online even after the deadline for the assignment has passed.

Schedule*

*Schedule might change during the semester.

Acknowledgements

The slides in this class are heavily based on the slides from other instructors. Specifically, many slides are the exact or modified version of the slides by Alexei A. Efros, James Hays, and Rob Fergus, who in turn have used materials from Steve Seitz, Rick Szeliski, Paul Debevec, Stephen Palmer, Paul Heckbert, David Forsyth, Steve Marschner, Fredo Durand, Bill Freeman, and others, as noted in the slides. The instructor gives full permission to use these slides for academic and research purposes, but please maintain all the acknowlegements.