CS 536 Computer Graphics

Course Page : http://www.cs.drexel.edu/~david/Classes/CS536

Suggested Textbooks:

It is University policy that you read your official Drexel email; it is the course policy that you read it at least once per day.

Course Objective

Computer Graphics represents a vast technical field, ranging from mathematics and geometry topics to computer hardware and software engineering topics to rendering, animation and virtual reality, far more material than can be comprehensively covered in a 10 week term. CS 536 Computer Graphics is designed to provide graduate students with an introduction to the geometric modeling aspects of computer graphics, as well as the related topic of transformations. Course material will cover the various representations for 3D curves, surfaces and solids, and will also discuss the creation of complex, hierarchical models. Material on general topics in computer graphics, e.g. drawing/clipping algorithms, color, viewing and rendering, will also be interspersed throughout the class in order to expand its coverage.


Like the other introductory CS graduate classes, this one requires that you have a basic background in computer science. You can demonstrate this by either having a computing related undergraduate degree, or by taking our pre-core classes, CS 520, 570 and 571. You will find this course extremely difficult if you do not have strong (B or better) linear algebra and multi-dimensional calculus skills. Minimal review of the relevant mathematics background will be given in this class. Students are assumed to have excellent knowledge of programming. Students can use whatever programming language they wish (C, C++, Java, Python, etc.) for the assignments in this class with the following caveat: you will need to turn in both source code and a makefile or script for testing and evaluation. Code must run as a single command-line process on the CS Department's Linux (tux) computers, without needing special libraries. Arguments passed to the command-line will parameterize assignments; hence you'll need to read command-line arguments (argc, argv) in arbitary order and parse input files. This course is mathematically intense and implementationally challenging. You will be required to implement complex data structures and mathematical calculations as a regular part of your assignments.

Course Grading Scheme

Graduate Students

  • Assignments (70%)
  • Presentation (10%)
  • Final exam (20%)
I intend to use the standard grading scale of 100→ 90 (A), 89→ 80 (B), 79→ 70 (C), 69→ 60 (D), else (F).
Also note that incompletes will not be given for this course.


Students must work on the assignments individually. No geometry or graphics libraries may be used in the homework assignments.
You may use math libraries to represent and manipulate vectors and matrices, command line option processing libraries, and libraries to write Open Inventor.
But they must be installed on tux!

Assignments that do not meet the program specifications EXACTLY will not be graded! Any assignments that are returned to students because they do not meet the assignment specifications will be penalized with late points.

Assignment results will be assessed visually. I am not looking for any specific file output.

1 point per day (max of 5 points, out of 10) will be deducted from late assignments.
The deadline for turning in all assignments is December 9.
You will be given a grade of 0 if an assignment is not turned in by this date.

The programming assignments should be submitted on the class Bb Learn page before 11:59 PM on the due date to be considered on-time.

All assignments will be run in the Unix Command Line Interface (CLI) on tux and will generate geometry files in the ASCII Open Inventor format. Examples of Open Inventor files can be found here. Inventor (*.iv) files can be viewed with an open-source CAD system called FreeCAD. Go here to download a version of this sofware for your computer. You must ensure that your Inventor files can be displayed in FreeCAD.

All assignments should include source code files, a README file and possibly a makefile (if you're writing in a compiled language).

No extra credit assignments will be offered!

Academic Honesty

You must be the sole original author of all assignments and examination solutions in their entirety, unless the instructor explicitly instructs you otherwise in written directions on an assignment or exam. Collaborative work is a violation of academic honesty in this course. You are not to examine or use code belonging to someone else, nor may you let anyone else examine or copy your code.

Students found in violation of the Academic Honesty policy will receive an 'F' in the class. In the case of plagiarism, all parties involved will be equally penalized.

The description of the department's Academic Integrity Policy can be found here. If a student violates this policy, an Alleged Academic Misconduct Report will be filed with the college.

It is your responsibility to avoid violating the university's policy. If you are unclear as to what the policy means in a particular situation, ask the instructor for clarification before you hand anything in.

See the examples below for clarification of this policy.


The following are acceptable:
  • Using code provided in lecture: include comments that cite the source.
  • Using code provided in the class textbook: include comments that cite the source.
  • Code developed jointly with instructor or teaching assistants assigned to this course.
  • Discussing algorithms or possible approaches to writing your program, WITHOUT discussing particulars of the code.
  • Discussing how to resolve errors, WITHOUT discussing particulars of the code.
These are NOT acceptable:
  • You borrow a printed or electronic copy of a friend's assignment, and use it for "inspiration".
  • You give a printed or electronic copy of your assignment to somebody else.
  • You "find" a copy of somebody's program in the trash, on a lab machine, on their hard drive, etc., and use it for "inspiration".
  • You pay a "tutor" who writes the assignment for you.
  • You download code from the Web, and turn in some or all of it as your own assignment.
  • You and a friend together write one assignment, then create separate modifications to be handed in.
  • You and a friend write certain portions of the assignment individually, but collaborate on other portions of the assignment.
  • You work in a group that works out the detailed structure of the assignment and you turn it into a specific program.
The College of Computing and Informatics has a "2 Strikes You're Out" policy.
If you have two cheating infractions, you will be expelled from your CCI major.

Your source code for all programming assignments will be run through a plagiarism detection system. This program uses compiler techniques, which are invariant of syntax and style. If you are sharing/borrowing code with other classmates (from this or previous years), you will get caught.


Each graduate student will read a technical conference paper related to geometric modeling or geometry processing and submit a Powerpoint presentation that describes/summarizes the paper.
Suggested conferences are the SIGGRAPH Conference, SIGGRAPH Asia Conference, Shape Modeling International Conference, Solid and Physical Modeling Conference and the Symposium on Geometry Processing. The paper must be from the main SIGGRAPH or SIGGRAPH Asia Conference, not just from any ACM SIGGRAPH-sponsored conference, symposium or workshop.
The presentation should include:

  • at least 10 slides
  • images
  • the citation information for the paper, i.e. where and when was the paper published, and by whom. Included on the title slide.

If you are not on a drexel.edu computer you will have to access the papers through the Drexel Library, or by connecting to the Drexel network via VPN.
Please no "Games Papers".

Here is a good example of what I expect.

The deadline for submitting the Powerpoint presentation is November 2.
The same policy as programming assignments applies for late presentations.


There will be a final exam on the material from class that is NOT covered by the regular assignments.

The in-class exam will be given on Wed. 12/12 at 6PM in Rush 213
It will be a 2 hour exam.

Final Exam Topics

Lectures Are Recorded

Recorded lectures can be accessed through the Class Capture link on the class Bb Learn page.

Week 1 (September 24 - 28)
  • Reading Assignment
    • Foley et al.: Chapter 1, 5.1, 9.2→9.2.1, 9.2.3
    • Mortenson: Chapter 1.1→1.5, 2.1→2.3, 4.1→4.2
  • September 26 - Lecture (6 per page) : Introduction
  • September 26 - Lecture (6 per page) : Math Review; Introduction to Curves
Week 2 (October 1 - October 5)
Week 3 (October 8 - 12)
Week 4 (October 15 - 19)
Week 5 (October 22 - 26)
Week 6 (October 29 - November 2)
Week 7 (November 5 - November 9)
Week 8 (November 12 - 16)
  • No in-class lecture this week!
  • Reading Assignment
    • Foley et al.: Chapter 5.2→5.9, 6.7, 7.1, 7.4→7.6
  • November 14 - Lecture (6 per page) : 2D and 3D Transformations
  • November 14 - Lecture (6 per page) : Hierarchical Models
Week 9 (November 19 - 23)
  • No Class
Week 10 (November 26 - 30)
  • Reading Assignment
    • Foley et al.: 6→6.2, 6.4, 12→12.2, 12.3.3, 12.4, 13, 14→14.2
  • November 26 - Assignment 4 Due
  • November 28 - Lecture (6 per page) : Introduction to 3D Viewing
  • November 28 - Lecture : Scanline Rendering
  • November 28 - Lecture (6 per page) : Culling, Z-Buffering and Ray Tracing
Week 11 (December 3 - December 7)

File last modified on December 5, 2018.