COMS W4167 Computer Animation
Fall 2021, Columbia University
TR 4:10pm-5:25PM, 1127 . Instructor: (http://www.cs.columbia.edu/~cxz)
Important! You will be using Codio (https://codio.com/) for doing and submitting your programminga assignments. In this way, every student will have the same programming environment to work with. We are also going to release start codes and solution executables on the Codio. More details will be announced on Courseworks (https://courseworks.columbia.edu/welcome).
Pre-requisites: Conformable on programming in C++, Data structures (tree, queue, etc.), Multivariable calculus (e.g., knowing the concepts of partial derivative, gradient, Jacobian), Linear algebra (vector, matrix)
Staff
Mandeep Fisher
(uni: mb4463) (uni: dc3505) (uni: jf3148)
Office Hours (https://piazza.com/columbia/fall2021/comsw4167_001_2021_3computeranimation/staff)
(Tentative) Schedule
date
9 Sep 14 Sep 16 Sep 21 Sep 23 Sep 28 Sep 30 Sep
5 Oct
7 Oct 12 Oct 14 Oct 19 Oct 21 Oct 26 Oct 28 Oct
topic
Intorduction
Kinematics
Time integration: Symplectic Euler Forces
Time integration: Implicit Euler Time integration: Implicit Euler Time integration: Implicit Euler Collision detection & response Particle clouds
Continuous collision detection Broad phase collision detection Broad phase collision detection Broad phase collision detection Constrained mechanical systems Rigid body kinematics
reading
assignments
2 Nov 4 Nov 9 Nov
11 Nov 16 Nov 18 Nov 23 Nov 25 Nov 30 Nov
2 Dec 7 Dec 9 Dec
———–
Rigid body kinematics
Rigid body collisions
Elasticity
Elasticity
Animation Control
Fluids: advection and total derivative ———–
Fluids: divergence free vector fields Fluids: free surfaces
Fluids: Other simulation methods Advanced topics
Projects and Work Load
Throughout this semester, you will have weekly programming assignments organized in a series of themes (see below). Each theme will have one or more milestones that you need to reach in your assignment submissions. For each assignment, we will provide starter code in C++. All projects should be submitted electronically to Codio (https://codio.com/). More details about finishing your assignments on Codio will be provided by CAs.
Theme 1 Mass Spring System
Theme 2 Krusty’s Crazy Collisions
Theme 3 Rigid Body Simulation
Theme 4 Elastic Body Simulation
Theme 5 Fluids
Take-home exam
Exams
There will be no midterm exam in this course. There will be a take-home final exam.
References
There is no required textbook. In case you need to refresh your Calculus and Linear Algebra background, here are some reference books:
‘s Calculus textbook (http://ocw.mit.edu/resources/res-18-001-calculus-online-textbook-spring- 2005/textbook)
A free linear algebra (http://linear.ups.edu/download/fcla-3.40-tablet.pdf) book online
We don’t expect you to know OpenGL; our starter code handles all the OpenGL rendering of objects for you. So you won’t learn OpenGL in this class. If you want to create your own scences with advanced OpenGL features, here are some references:
OpenGL reference page (https://www.opengl.org/sdk/docs)
OpenGL “Red Book” (http://www.glprogramming.com/red) — *the* reference for OpenGL programming ‘s OpenGL “tutors” (http://www.xmission.com/~nate/tutors.html) programs
Anton’s OpenGL 4 tutorials (http://antongerdelan.net/opengl)
About COMS W4167
Grading: We strive to maintain a fast, transparent and fair grading process:
There will be weekly assignments called “milestones”.
You will submit the completed milestone every week.
Each weekly milestone is assigned with equal weight for your final grade of the class.
If an assignment is submitted multiple times before the deadline, only the most recent submission will be graded. Milestones will be clustered into themes (this does not affect grading). There will be approximately 5 themes. There will be no midterm exam, no final project. Instead, there will be a take-home final exam.
Your final numerical grade will be an average of the numerical grades of all themes. The numerical grade of a theme will be an average of the numerical grades of all milestones in that theme.
Due dates: Weekly deadlines are due on the date and time indicated in the assignment handout, usually at 10:00PM of the day. They must be submitted electronically, as detailed in the assignment.
Lateness policy: Late submissions lose 1% per six minutes of lateness. For example: a submission that is two hours late is penalized 20%, and a submission that is ten hours late receives no credit. Rationale: Since weekly milestones build on each other, we must ensure that all students begin each week at an equal playing field. By enforcing a strict lateness policy, we will be able to post the solution to each milestone shortly after it 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, job interviews, etc. Plan ahead.
Curving and Final Grade: This class will *not* be curved down. A student achieving a certain percentage grade has a guaranteed minimum letter grade. We reserve the right to curve all grades uniformly upward (improving your letter grade) subject to our discretion. The minimum grade distribution for this class will be given by evaluating the student’s numerical grade, after adjusting for lateness and extra credit, following the table
A: 90% or higher B: 80% to 89% C: 70% to 79% D: 60% to 69%
with modifiers (+ and -) left to the instructor’s discretion subject to considerations such as relative ranking to other students, quality of submitted code, uniformity of quality across assignments, engagement in the class.
Questions, help, discussion: The instructors and TAs 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 (https://piazza.com/class/kta7z4zpa6l1ob) (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.
Cases that violate the academic integrity include (not exclusively):
Submit work that is not original
Publish code or solutions online
Post the course questions on forums including stack overflow
Submit someone else¡¯s work, or a modification of that work, with or without that person¡¯s knowledge Allow someone else to submit his/her work, or a modification of that work
Solve as a group a quiz or project
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 TAs, 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
(http://gradengineering.columbia.edu/academic-integrity-0).
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.