COMS W4160 Computer Graphics

Spring 2021, Columbia University

TR, 4:10PM-5:25PM

Staff

Hayun Chong (CA, hc2978@columbia.edu)

TBD

Schedule

(The lecture slides will be made availabe right before the lecture through courseworks.)

date		topic
14	Jan	Introduction
19	Jan	Linear algebra
21	Jan	Geometric transformation
26	Jan	Geometric transformation
28	Jan	3D Rotation and Quaternion
2	Feb	Introduction and Demo of OpenGL
4	Feb	Graphics Pipeline
9	Feb	Graphics Pipeline II
11	Feb	GSLS Shaders and Shading Models
16	Feb	Texture Mapping
18	Feb	Mipmap Texture
23	Feb	Ray Tracing
25	Feb	Ray Tracing and Radiosity
2	Mar	-----------
4	Mar	-----------
9	Mar	Rendering Equation
11	Mar	Monte Carlo Integration
16	Mar	Monte Carlo Sampling
18	Mar	Triangle Meshes
23	Mar	Triangle Mesh Manipulation
25	Mar	Character Animation
1	Apr	Forward Kinematics
6	Apr	Interpolation and Spline Curves
8	Apr	Interpolation of Quaternion
13	Apr	Inverse Kinematics
15	Apr	Color

Projects and Work Load

The workload of this class starts with a paper homework with a few mathematical problems, followed by 4 programming assignment throughout the semester and a final exam. For the programming projects, you will be asked to implement some computer graphics algorithms. All programming assignment should be implmented in Java and will be submitted to courseworks.

Paper assignment

TBD

Project 1 Hello World with OpenGL

TBD

Project 2 Play with GLSL Shaders

TBD

Project 3 Monte Carlo Rendering

TBD

Project 4 Mesh Manipulation

TBD

Exams

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

About COMS W4160

Grading: Each homework to be graded will be scored on a 100-point scale. Your final grade will be a weighted average of the grades of the assignments and your final exam. The paper homeworks will account for 10% of the grade, the program assignments will account for 75% (PA1: 12%, PA2: 13%, PA3: 25%, PA4: 20%), and the final exam will account for 15%. For each assignment, you'll have about two weeks to finish them. The execption is PA3, which will be split into multiple sub-assignments and will take a longer time. The final exam will be a take-home exam.

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 handout.

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.