CSC 433/533 - Computer Graphics

Course Syllabus



Description of Course

Theory and practice of computer graphics: basic graphics programming, 2D and 3D transformations, clipping, 2D and 3D viewing, hierarchical modeling, hidden surface removal, lighting and shading, color, ray-tracing, radiosity, curve and surface modeling, and animation.

Course Prerequisites or Co-requisites

Students are expected to have advanced programming skills in C++ and introductory knowledge of linear algebra and calculus. For undergraduates, this includes CSC 252 (Computer Organization), CSC 335 (Object-Oriented Programming and Design), CSC 345 (Analysis of Discrete Structures), CSC 352 (Systems Programming and Unix), and MATH 215 (Linear Algebra) or MATH 313 (Introduction to Linear Algebra). While students majoring in areas other than CSC are encouraged to enroll, certain topics may prove challenging. Please contact the instructor if you are unsure if you satisfy the prerequisites.

Instructor and Contact Information

Course Format and Teaching Methods

Primarily, the format is driven by lectures combined with in-class discussion. Out-of-class activities include readings in relevant textbooks and research papers, programming assignments, take-home exercises, and online discussions.

Course Objectives and Expected Learning Outcomes

This course will cover both a theoretical understanding and practical application of computer graphics concepts. Students will be expected to:



Course Content

Location

Lecture Topics

Week Date Monday Date Wednesday
1 Jan 08 -- No Class -- Jan 10 Introduction
2 Jan 15 -- MLK Day -- Jan 17 Raster Images
3 Jan 22 Color and Perception Jan 24 Signal Processing 1
4 Jan 29 Signal Processing 2 Jan 31 Tone Reproduction
5 Feb 05 Ray Tracing 1 Feb 07 Ray Tracing 2
6 Feb 12 Ray Tracing 3 Feb 14 Ray Tracing 4
7 Feb 19 Triangle Meshes Feb 21 -- Cancelled --
8 Feb 26 Acceleration Structures Feb 28 Midterm Exam
9 Mar 05 -- Spring Break -- Mar 07 -- Spring Break --
10 Mar 12 Textures Mar 14 Transformations
11 Mar 19 Viewing Mar 21 Graphics Pipeline 1
12 Mar 26 Graphics Pipeline 2 Mar 28 Curves 1
13 Apr 02 Curves/Surfaces Apr 04 Animation 1
14 Apr 09 Animation 2 Apr 11 Animation 3
15 Apr 16 Implicit Modeling 1 Apr 18 Implicit Modeling 2
16 Apr 23 MC Sampling Apr 25 Global Illumination
17 Apr 30 Image Compositing May 02 Final Exam Review


Required Texts and Readings

Assignments and Examinations

Assignments

This course will involved 6 assignments, each spanning approximately two (or occasionally three) weeks from posting date to due date. All assignments will have two components: a written component and a related programming exercise. The programming component will be completed in C++, built with CMake, and occassional rely on external libraries such as the Simple DirectMedia Layer.

Name Topic Post Date Due Date Graded Date Percent
Assignment 01 Image Basics Jan 17 Jan 28 Feb 04 3
Assignment 02 Images Jan 29 Feb 13 Feb 20 10
Assignment 03 Ray Tracing Feb 14 Mar 11 Mar 18 12
Assignment 04 Shapes Mar 12 Mar 25 Apr 01 10
Assignment 05 Rasterizer Mar 26 Apr 15 Apr 22 10
Assignment 06 Animation Apr 16 May 02 May 06 10
Total Assignment Percentage: 55


Class Participation

This class participation grade is the instructor’s subjective judgement of the student’s contribution to a lively classroom atmosphere. He will consider mainly active, informed participation in classroom discussions, and homework reviews. Frequently, the instructor expects to conduct regular Obviously, students not attending class are not contributing in this way.

Midterm Examination

A midterm exam will be held in class on Wednesday, February 28th, and it will cover all material discussed in class prior to the date of the examination. The written portions of assignments will provide sample questions.

Final Examination

The final examination will be comprehensive. The written portions of assignments will provide sample questions and a review will be conducted on the final lecture.

Exam Date/Time/Location: Thur., May 10, 1-3pm, 906 Gould-Simpson

See also,

Submission, Lateness, and Revision Policy

All assignments have a fixed due date. Revisions and resubmissions after grading will not be accepted.

Submission for assignments will be due on 11:59:59PM of the due date unless otherwise noted. A late submission will receive a penalty of 10% per day for each work day it is late, up to a maximum of 5 days late. Grades for assignment submitted late may not be posted within the same time frame as assignments submitted on time, but the instructor will make their best effort to expedite the grading of late submissions.



Course Policies

Absence and Class Participation Policy

The UA’s policy concerning Class Attendance, Participation, and Administrative Drops is available at http://catalog.arizona.edu/policy/class-attendance-participation-and-administrative-drop

The UA policy regarding absences for any sincerely held religious belief, observance or practice will be accommodated where reasonable: http://policy.arizona.edu/human-resources/religious-accommodation-policy.

Absences preapproved by the UA Dean of Students (or dean’s designee) will be honored. See https://deanofstudents.arizona.edu/absences.

Participating in the course and attending lectures and other course events are vital to the learning process. That said, attendance is not required for lectures. Students who miss class due to illness or emergency are not required to bring documentation from their health-care provider or other relevant, professional third parties. Nevertheless, class participation is an important part of your grade in this course, and it is impossible for a student to participate and the instructor to gauge participation if a student does not attend.

Late Instructor

Your instructor will make every effort to be in class on time, or to inform you of any delay or cancellation. In the unusual event that he should not arrive in class or send word by 15 minutes from the class start time, the class is officially cancelled.

Makeup Policy for Students Who Register Late

Students who register after the first class meeting may make up missed assignments/quizzes at a deadline set in consultation with the instructor.

Course Communications

We will use official UA email and Piazza as the primary mode of contact. D2L will be used only for the instructor to securely distribute grades to students.

Grading Scale and Grading Policies

Grades will be assigned based on the following scale:

Grading will be based on performance on the set of assignments, the midterm and final exam, and class participation:

Each assignment description will include a specific rubric for how it is graded, typically out of a score between 0 and 100. Scores on such assignments will be weighted according to the relative point value of each assignment as highlighted above.

While the above grading scale is identical for students in both 433 and 533, students in the 533 section will complete different assignments that are due on a similar timeline.

Department of Computer Science Grading Policy

  1. Instructors will explicitly promise when every assignment and exam will be graded and returned to students. These promised dates will appear in the syllabus, associated with the corresponding due dates and exam dates.
  2. Graded homework will be returned before the next homework is due.
  3. Exams will be returned “promptly”, as defined by the instructor (and as promised in the syllabus).
  4. Grading delays beyond promised return-by dates will be announced as soon as possible with an explanation for the delay.

Requests for incomplete (I) or withdrawal (W)

Request must be made in accordance with University policies, which are available at http://catalog.arizona.edu/policy/grades-and-grading-system#incomplete and http://catalog.arizona.edu/policy/grades-and-grading-system#Withdrawal, respectively.

Dispute of Grade Policy

After receiving any grade for any submission, a student has 24 hours to respond to the instructor with any disputes in an email with the subject “Grade Dispute”. Such a response must enumerate a specific set of disputed items for the submission and provide evidence that each item was improperly graded. The instructor will then completely regrade the entire submission, including both the disputed items as well as non-disputed items, with the potential for all aspects of the grade to change.



Department and University Policies

Department of Computer Science Code of Conduct

The Department of Computer Science is committed to providing and maintaining a supportive educational environment for all. We strive to be welcoming and inclusive, respect privacy and confidentiality, behave respectfully and courteously, and practice intellectual honesty. Disruptive behaviors (such as physical or emotional harassment, dismissive attitudes, and abuse of department resources) will not be tolerated. The complete Code of Conduct is available on our department web site. We expect that you will adhere to this code, as well as the UA Student Code of Conduct, while you are a member of this class.

Classroom Behavior Policy

To foster a positive learning environment, students and instructors have a shared responsibility. We want a safe, welcoming, and inclusive environment where all of us feel comfortable with each other and where we can challenge ourselves to succeed. To that end, our focus is on the tasks at hand and not on extraneous activities (e.g., texting, chatting, reading a newspaper, making phone calls, web surfing, etc.).

Students are asked to refrain from disruptive conversations with people sitting around them during lecture.

Some learning styles are best served by using personal electronics, such as laptops and iPads. Nevertheless, these devices can be distracting to other learners. While all students are welcome to use personal electronics in class, they must be used in a way that does not disrupt either the instructor or other students’ experience.

Students observed engaging in disruptive activity will be asked to cease this behavior. Those who continue to disrupt the class will be asked to leave lecture or discussion and may be reported to the Dean of Students.

Threatening Behavior Policy

The UA Threatening Behavior by Students Policy prohibits threats of physical harm to any member of the University community, including to oneself. See http://policy.arizona.edu/education-and-student-affairs/threatening-behavior-students.

Content Warning

While the instructor does not intend to include topics and/or course material includes content that are explicit or offensive in any way. The instructor will make every effort to provide advance notice when such materials may potentially be or potentially violate this intent. Please contact the instructor to discuss any content-related concerns, as alternative materials may be available.

Accessibility and Accommodations

At the University of Arizona we strive to make learning experiences as accessible as possible. If you anticipate or experience physical or academic barriers based on disability or pregnancy, you are welcome to let me know so that we can discuss options. You are also encouraged to contact Disability Resources (520-621-3268) to explore reasonable accommodation.

If our class meets at a campus location: Please be aware that the accessible table and chairs in this room should remain available for students who find that standard classroom seating is not usable.

Code of Academic Integrity

Students are encouraged to share intellectual views and discuss freely the principles and applications of course materials. However, graded work/exercises must be the product of independent effort unless otherwise instructed. Students are expected to adhere to the UA Code of Academic Integrity as described in the UA General Catalog. See http://deanofstudents.arizona.edu/academic-integrity/students/academic-integrity.

The University Libraries have some excellent tips for avoiding plagiarism, available at http://www.library.arizona.edu/help/tutorials/plagiarism/index.html. Publicly available sources for code or other material, in small amounts, may be freely used if appropriately attributed. A good rule of thumb: when in doubt about whether the use of small snippets of code not your own in a programming assignment is allowed, first ask the instructor.

Selling class notes and/or other course materials to other students or to a third party for resale is not permitted without the instructor’s express written consent. Violations to this and other course rules are subject to the Code of Academic Integrity and may result in course sanctions. Additionally, students who use D2L or UA e-mail to sell or buy these copyrighted materials are subject to Code of Conduct Violations for misuse of student e-mail addresses. This conduct may also constitute copyright infringement.

UA Nondiscrimination and Anti-harassment Policy

The University is committed to creating and maintaining an environment free of discrimination; see http://policy.arizona.edu/human-resources/nondiscrimination-and-anti-harassment-policy

Our classroom is a place where everyone is encouraged to express well-formed opinions and their reasons for those opinions. We also want to create a tolerant and open environment where such opinions can be expressed without resorting to bullying or discrimination of others.

Additional Resources for Students

UA Academic policies and procedures are available at http://catalog.arizona.edu/policies

Student Assistance and Advocacy information is available at http://deanofstudents.arizona.edu/student-assistance/students/student-assistance

Confidentiality of Student Records

See http://www.registrar.arizona.edu/personal-information/family-educational-rights-and-privacy-act-1974-ferpa?topic=ferpa

Subject to Change Statement

Information contained in the course syllabus, other than the grade and absence policy, may be subject to change with advance notice, as deemed appropriate by the instructor.