COMS W4160 Computer Graphics

Spring 2017, Columbia University

TR 11:40pm-12:55PM, 1127 Seeley W. Mudd Building

Instructor: Changxi Zheng

Staff

Chang Xiao                  (Ph.D. IA, cx2180@columbia.edu)
Henrique Maia             (Ph.D. IA, htm2104@columbia.edu)
Lucas Schuermann     (IA, lvs2124@columbia.edu)

Office Hours

Schedule

date topic reading assignments
19Jan Introduction (slides)    
24Jan Linear, Affine, and Frames (slides) [S&M] Chap. 2 & 5; [Go.] Chap. 2 & 3  
26Jan Geometric Transformation (slides) [S&M] Chap. 6  
31Jan Geometric Transformation (slides) Big Buck Bunny developement files paper assignment is out
2Feb Introduction to OpenGL    
7Feb 3D Rotation and Quaternions (slides) Quaternion interpolation PA1 is out
9Feb --- Cancelled due to snow storm ---    
14Feb Geometric Transformations in Graphics Pipeline (slides) [S&M] Chap. 7  
16Feb Graphics Pipeline (slides) [S&M] Chap. 8  
21Feb Graphics Pipeline and Shaders (slides)    
23Feb GLSL Introduction GLSL 3.30 Spec.  
28Feb Texture (slides) Texture mapping in LWJGL PA2 is out
2Mar MipMap Texture (slides) MipMap level estimation  
7Mar Ray Tracing & Rendering Equation (slides)    
9Mar Monte Carlo Rendering (slides)    
14Mar -----------    
16Mar -----------    
21Mar Monte Carlo Rendering: Sampling Methods (slides)   PA3 is out
23Mar Monte Carlo Rendering: Sampling Methods (slides)  
28Mar Triangle Meshes (slides) photon mapping tutorial  
30Mar Triangle Mesh Manipulation    
4Apr Interpolation and Spline curves    
6Apr Bezier Splines    
11Apr Forward Kinematics    
13Apr Inverse Kinematics    
18Apr Triangle Meshes    
20Apr Preliminary of physics-based simulation    
25Apr Introduction to Advanced Rendering    
27Apr Color    

Projects and Work Load

You fun of this class starts from a paper homework with a few mathematical problems, followed by 4 programming projects throughout the semester and a final project. For the programming projects, you will be asked to implement some computer graphics algorithms. For the final project, you will propose a project which involves computer graphics techniques that you learn in this class. All projects should be implmented in Java and will be submitted to courseworks.

The assignment handout has been released on Courseworks.
Due date: 10pm, Feb. 5 (Sunday)
Please submit electronically on Coureworks.
The assignment handout has been released on Courseworks.
Due date: 10pm, Feb. 24
Please submit electronically on Coureworks.
The assignment handout has been released on Courseworks.
Due date: 10pm, Mar. 12 (before the Spring break).
5% bonus if last submission is turned in by 10PM, Mar. 10.
Please submit electronically on Coureworks.
The assignment handout has been released on Courseworks.
Due date: 10pm, Apr. 2.
Please submit electronically on Coureworks.
TBD
TBD
TBD

Exams

There will be no mid-term or final exam in this course. But there will be a final project.

Recommended Textbook


Shirley & Marschner,
Fundamentals of Computer Graphics
third edition

Supplemental books and materials:


Gortler,
Foundations of 3D Computer Graphics
first edition

About COMS W4160

Grading: Each homework to be graded will be scored out of 4 points on a 4.5-point scale:

Your final grade will be a weighted average of the grades of the assignments and your final project. The paper homeworks will account for 10% of the grade, the program assignments will account for 70% (14% each), and the final project will account for 20%. The midterm prelim will cover the first half of the course. The format will be similar to paper homeworks, textbook material and questions. It will be closed book, but you are allowed to bring one letter-sized piece of paper with writing on both sides, to avoid the need to memorize details.

Due dates Paper homework should be handled in after the lecture on the due date. Programming assignments are due at 10:00 pm on the due date and are accepted with a late penalty. They must be submitted electronically, as detailed in the assignment.

Lateness policy: Late submissions lose 1% per 12 minutes of lateness. For example: a submission that is two hours late is penalized 10%, and a submission that is 20 hours late receives no credit. Rationale: Since some programming assignments are built on each other, we must ensure that all students begin each assignment at an equal playing field. By enforcing a strict lateness policy, we will be able to post next assignment shortly after the previous one is due, thereby enabling students to build on a solid foundation in the following week.
Plan ahead. The only exception to this policy is a documented medical emergency. In order to ensure fair grading, exceptions are not possible for holidays, sport meets, theater appearances, indigestion, etc. Plan ahead.

Questions, help, discussion: The instructors and IAs are available to answer questions, advise on projects, or just to discuss interesting topics related to the class at office hours and by appointment as needed. For electronic communication we are using Piazza (link also available at the top of this page). Please sign up for the Piazza page. When posting questions, please keep them organized by posting them to specific folders.

You are welcome (encouraged, even) to discuss the homeworks and projects among yourselves in general terms. But when you start writing up the homeworks or implementing the projects, you need to be working alone. In particular, it is never permitted for you to see another student's homework writeup or other's program code, and certainly never tolerated to copy parts of one person's writeup, code, or results into another's, even if the general solution was worked out together.

You're also encouraged to read any published sources—books, articles, public web sites—that help you learn. If you find an idea in one of these sources that becomes part of your solution (or even gives you the whole solution), that's fine, but it is imperative that you explicitly cite the source on your homework or state it in a comment of your code. Otherwise you would be falsely claiming to have invented the idea yourself.

Academic integrity: We expect complete integrity from everyone. We assume the work you hand in is your own, and the results you hand in are generated by your program. You're welcome to read whatever you want to learn what you need to do the work, but we do expect you to build your own implementations of the methods we are studying. If you're ever in doubt, just include a citation in your code or report indicating where some idea came from, whether it be a classmate, a web site, another piece of software, or anything—this always maintains your honesty, whether the source was used in a good way or not. The principle is that an assignment is an academic document, like a journal article. When you turn it in, you are claiming that everything in it is your original idea (or is original to you and your partner, if you're handing in as a pair) unless you cite a source for it. it's never OK for you to see another student's homework writeup or another team's program code, and certainly never OK to copy parts of one person's or team's writeup, code, or results into another's, even if the general solution was worked out together.

School can be stressful, and your coursework and other factors can put you under a lot of pressure, but that is never a reason for dishonesty. If you feel you can't complete the work on your own, come talk to the professor or the IAs, or your advisor, and we can help you figure out what to do. Think before you hand in!

Clear-cut cases of dishonesty will result in failing the course.

For more information see Columbia Engineering's Code of Academic Integrity.

Open Door Policy: We hope the course to run smoothly and enjoyably. Feel free to let us know if you find the course helpful and interesting. Especially, let us know sooner about the reverse. Drop by our office hours, leave us a note, or send us an email.