computer graphics assignment with solution

Ruben Partono, Fall 2020

Browse gallery

Clara Kang Fall 2018

Dave Pagurek, Spring 2018

Monica Luo, Spring 2017

Nick Frasser, Fall 2016

Richard Ye, Winter 2015

Cs 488/688: introduction to computer graphics.

Welcome to the home page for CS488/688, the introductory computer graphics course in the School of Computer Science at the University of Waterloo . This course focuses on 3D graphics and relevant topics in computer graphics.

• Explain the algorithmic and mathematical concepts used in computer graphics.
• Write interactive programs that display and manipulate 3D geometry.
• Write a ray tracing system and an interactive graphics application using OpenGL.
• The website realtimerendering.com lists a bunch of books that are free online. Among others, for ray tracing, we recommend the pbrt book as a general reference and Peter Shirley's e-books as a good supplementary material for ray tracing.
• The graphics codex can serve as a reference to the topics and tools used in graphics.
• The website open.gl can be a good starting point for programming in modern OpenGL.
• A longer sequence of tutorials at learnopengl.com goes into more detail about specific topics in OpenGL.
• Song Ho Ahn also has a number of useful tutorials that explain concepts in 3D computer graphics, especially as related to the OpenGL graphics pipeline.
• Docs.gl for the OpenGL API reference.
• Terence's OpenGL tutorial slides .
• Inigo Quilez has several articles explaining practical solutions to many problems in graphics.
• The course note of CS 488/688 from the previous term is also available here for your reference.

Expectations

• Project proposal: 10%
• Project: 30%

Assignments

• This course has five assignments (A0 to A4) and the final project. Please read the additional notes regarding assignment completion and submission. These notes may help you avoid losing marks unnecessarily. You will submit your work via LEARN . Students should contact the TAs in case of any issue related to the submission procedure. Note that you will need to Students in CS 688 will have additional tasks in the project as explained below.
• Assignment 0 : Warmup (optional) Due September 17th at 10:00 AM ET
• Assignment 1 : OpenGL Due September 27th at 10:00 AM ET
• Assignment 2 : Pipeline Due October 6th at 10:00 AM ET
• Assignment 3 : Puppet Due October 27th at 10:00 AM ET
• Assignment 4 : Trace Due November 12th at 10:00 AM ET
• Project : Project Proposal due November 16th at 10:00 AM ET Corrected proposal due November 19th at 6:00 PM ET Project due December 7th at 10:00 AM ET
• The course will roughly follow the following schedule.
• Week 0 (Sep 8 - 10): Introduction
• Week 1 (Sep 13 - 17): Rasterization, Sampling and Reconstruction
• Sep 17: Assignment 0 due
• Week 2 (Sep 20 - 24): Transformations
• Week 3 (Sep 27 - Oct 1): Graphics pipeline, Textures
• Sep 27: Assignment 1 due
• Week 4 (Oct 4 - Oct 8): Real-time rendering techniques, Ray tracing basics
• Oct 6: Assignment 2 due
• Reading week (Oct 9 - Oct 17): No class
• Week 5 (Oct 18 - Oct 22): Cameras, Colors, Shading models
• Oct 27: Assignment 3 due
• Week 6 (Oct 25 - Oct 29): Acceleration data structures
• Week 7 (Nov 1 - Nov 5): Monte Carlo integration, Theory of light transport
• Week 8 (Nov 8 - Nov 12): Path tracing, Photon density estimation
• Nov 12: Assignment 4 due
• Week 9 (Nov 15 - Nov 19): Particles, Multibody dynamics
• Nov 16: Project proposal due
• Nov 19: Corrected project proposal due
• Week 10 (Nov 22 - Nov 26): Rigid bodies, Deformables
• Week 11 (Nov 29 - Dec 3): Participating media, Advanced topic
• Week 12 (Dec 6 - Dec 7): Conclusion
• Dec 7: Project due

Other University-related Information

Mental Health: If you or anyone you know experiences any academic stress, difficult life events, or feelings like anxiety or depression, we strongly encourage you to seek support.

• Campus Wellness https://uwaterloo.ca/campus-wellness/
• Counselling Services: [email protected] / 519-888-4567 ext 32655 / Needles Hall North 2nd floor, (NH 2401)
• MATES: one-to-one peer support program offered by Federation of Students (FEDS) and Counselling Services: [email protected]
• Health Services service: located across the creek from Student Life Centre, 519-888-4096.
• Good2Talk (24/7): Free confidential help line for post-secondary students. Phone: 1-866-925-5454
• Here 24/7: Mental Health and Crisis Service Team. Phone: 1-844-437-3247
• OK2BME: set of support services for lesbian, gay, bisexual, transgender or questioning teens in Waterloo. Phone: 519-884-0000 extension 213

Diversity: It is our intent that students from all diverse backgrounds and perspectives be well served by this course, and that students' learning needs be addressed both in and out of class. We recognize the immense value of the diversity in identities, perspectives, and contributions that students bring, and the benefit it has on our educational environment. Your suggestions are encouraged and appreciated. Please let us know ways to improve the effectiveness of the course for you personally or for other students or student groups. In particular:

• We will gladly honour your request to address you by an alternate/preferred name or gender pronoun. Please advise us of this preference early in the semester so we may make appropriate changes to our records.
• We will honour your religious holidays and celebrations. Please inform of us these at the start of the course.
• We will follow AccessAbility Services guidelines and protocols on how to best support students with different learning needs.

Academic Integrity: In order to maintain a culture of academic integrity, members of the University of Waterloo community are expected to promote honesty, trust, fairness, respect and responsibility. [Check https://uwaterloo.ca/academic-integrity/ for more information.]

Grievance: A student who believes that a decision affecting some aspect of his/her university life has been unfair or unreasonable may have grounds for initiating a grievance. Read Policy 70, Student Petitions and Grievances , Section 4. When in doubt please contact the department's administrative assistant who will provide further assistance.

Discipline: A student is expected to know what constitutes academic integrity [check https://uwaterloo.ca/academic-integrity/ ] to avoid committing an academic offence, and to take responsibility for his/her actions. A student who is unsure whether an action constitutes an offence, or who needs help in learning how to avoid offences (e.g., plagiarism, cheating) or about 'rules' for group work/collaboration should seek guidance from the course instructor, academic advisor, or the undergraduate Associate Dean. For information on categories of offences and types of penalties, students should refer to Policy 71, Student Discipline . For penalties check Guidelines for the Assessment of Penalties .

Appeals: A decision made or penalty imposed under Policy 70 (Student Petitions and Grievances) (other than a petition) or Policy 71 (Student Discipline) may be appealed if there is a ground. A student who believes he/she has a ground for an appeal should refer to Policy 72, Student Appeals .

MOSS (Measure of Software Similarities) is used in this course as a means of comparing students' assignments to ensure academic integrity. We will report suspicious activity, and penalties for plagiarism/cheating are severe. Please read the available information about academic integrity very carefully.

Discipline cases involving any automated marking system such as Marmoset or MarkUs include, but are not limited to, printing or returning values in order to match expected test results rather than making an actual reasonable attempt to solve the problem as required in the assignment question specification.

Note for Students with Disabilities: AccessAbility Services, located in Needles Hall, Room 1401, collaborates with all academic departments to arrange appropriate accommodations for students with disabilities without compromising the academic integrity of the curriculum. If you require academic accommodations to lessen the impact of your disability, please register with AccessAbility Services at the beginning of each academic term.

Intellectual Property: Students should be aware that this course contains the intellectual property of their instructor, TA, and/or the University of Waterloo. Intellectual property includes items such as:

• Lecture content, spoken and written (and any audio/video recording thereof);
• Lecture handouts, presentations, and other materials prepared for the course (e.g., PowerPoint slides);
• Questions or solution sets from various types of assessments (e.g., assignments, quizzes, tests, final exams);
• Work protected by copyright (e.g., any work authored by the instructor or TA or used by the instructor or TA with permission of the copyright owner).

Course materials and the intellectual property contained therein, are used to enhance a student's educational experience. However, sharing this intellectual property without the intellectual property owner's permission is a violation of intellectual property rights. For this reason, it is necessary to ask the instructor, TA and/or the University of Waterloo for permission before uploading and sharing the intellectual property of others online (e.g., to an online repository).

Permission from an instructor, TA or the University is also necessary before sharing the intellectual property of others from completed courses with students taking the same/similar courses in subsequent terms/years. In many cases, instructors might be happy to allow distribution of certain materials. However, doing so without expressed permission is considered a violation of intellectual property rights.

Please alert the instructor if you become aware of intellectual property belonging to others (past or present) circulating, either through the student body or online. The intellectual property rights owner deserves to know (and may have already given their consent).

Assignments and Grading

• Homework Schedule : Weekly homeworks are assigned Tuesday and due the following Monday.
• Evaluation : Grades will be 50% homeworks, 50% final project (ray traced image). The weekly graded homeworks are designed as building blocks towards the final ray traced image. There will be 8 homeworks, and they each count equally. For samples of student final projects from previous years, see the project showcase page .
• Collaboration : You may work with a partner for both the homeworks and the final ray traced image. You may change partners as often as you wish throughout the quarter. It is recommended but not required that you attend the grading sessions with your partner, if applicable. However, the CAs will ask independent questions -- the person being asked the question by the CA should answer.
• Rubric : Assignments will be graded on a 0-5 point basis. The rubric will be provided at the end of each homework's writeup. If your homework grades are not going well, then do not be surprised if your final image grade is lower than what you expect. Feedback is very important in computer graphics, so please take each homework seriously and attend the grading sessions each week.
• Late Assignments : As a general rule, no late assignments will be accepted . Exceptions will of course be made for unforeseeable circumstances and as required by university or departmental policy.

Hardware and Software

You are encouraged to do class assignments on your personal computer. Computers should contain a modern graphics card with at least 2 GB of free disk space to download and run Blender. Blender is readily available on Windows, Mac, and Linux platforms, and the starter code has been tested on all of these platforms.

Search code, repositories, users, issues, pull requests...

Provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

computer-graphics-assignment

Here are 7 public repositories matching this topic..., amey-thakur / computer-graphics-and-computer-graphics-lab.

CSC404: Computer Graphics [CG] & CSL402: Computer Graphics Lab [CG Lab] <Semester IV>

• Updated Mar 13, 2024

aeris170 / SuperQuadricRenderer

Bilkent University Computer Graphics course Assignment 3.

• Updated Apr 27, 2020

OfficialBishal / DreamyWorld

Computer Graphics Stick-Figure Project using Adobe Animate CC

• Updated Jan 24, 2020

oktaviacitra / final-project-computer-graphic

OPEN GL C++ ANIMATION

• Updated Jan 3, 2020

sonowz / graphics-demo

Self-study & Computer graphics class raytrace assignment demonstration

• Updated May 29, 2018

aeglon97 / Computer-Graphics

A software application similar to Paint

• Updated Sep 19, 2018

kvssandhu / CGM_practicals

IPU : GTBIT : Computer Graphics & Multimedia Programs in C

• Updated Dec 5, 2019

Improve this page

Add a description, image, and links to the computer-graphics-assignment topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the computer-graphics-assignment topic, visit your repo's landing page and select "manage topics."

COS 426: Computer Graphics

• Description

Computer graphics lies at the intersection of computer science, geometry, physics, and art. This course provides an introduction to the field, with an emphasis on practical methods and applications in image processing, modeling, rendering, and computer animation. The goal of this course is to equip students with the tools and techniques they need to build projects with significant graphical components; this includes applications for realizing artistic visions (art and architecture), user interaction (UI/UX development), entertainment products (video games, CGI, animations, and augmented reality), visualizations and academic research (physics, biology, chemistry, engineering, and other disciplines), etc.

Topics include: color theory, sampling, image processing, image compositing, mesh representations, mesh processing, parametric curves and surfaces, implicit surfaces, subdivision surfaces, geometric data structures, geometric transformations, ray casting, lighting and reflectance, global illumination, rasterization, scan conversion, particle systems, animation, computer games, fabrication, etc.

• Prerequisites

The course is appropriate for students who have taken COS 217 and COS 226, or have equivalent programming maturity. JavaScript will be the main programming language; however no prior knowledge of the language is required for students who wish to enroll in this course.

• Lectures and Precepts

Lectures are held on Tuesdays and Thursdays from 3:00 – 4:20 PM in Friend 101.

Precept is held on Thursday from 7:30 – 8:20 PM and Friday from 10:00 – 10:50 AM and 11:00 – 11:50 AM. Students are encouraged to attend their own precept, but may attend another precept during the week in case of a one-time conflict. Precept attendance is highly encouraged.

Please note: Precepts will not be held during the week of Thanksgiving. However, the regular Friday precepts will be held on December 9.

• Required Reading

There is one required textbook for this course:

Computer Graphics with OpenGL , 4th Ed., Hearn, Baker, and Carithers. Prentice Hall, 2010. ISBN: 978-0136053583.

In the past, most students have found it is possible to pass the course without opening the textbook once, as almost all graded material is provided through lecture and precepts. Nevertheless, this textbook will prove useful for especially eager and motivated students who wish to pursue further studies in computer graphics. In addition to covering graphics concepts that could not be squeezed into this course, the textbook contains C++ and OpenGL implementations that will be of use to graphics practitioners.

Staff contact information is listed below, but students seeking help should keep in mind that it is almost always more appropriate to post their question to Ed rather than emailing an individual member of the course staff.

Szymon Rusinkiewicz

• Office Hours

TTh after class, or calendly.com/smr-princeton

Graduate TA

Guðni Gunnarsson

Fri 1:30 pm - 3:30 pm at CS 003

Yuanqiao Lin

Fri 3:30 pm - 5:30 pm at CS 003

Yuting Yang

Wed 4pm - 6pm at CS 003

The precepts for this class are geared towards assisting students with their assignments, and students are urged to study the precept materials before class and come prepared with questions. These precept materials generally consist of “tips and tricks” slides for the current assignment, and it is highly recommended that students read through an assignment’s precept slides (in their entirety) before starting work on the assignment itself. Part of precept will be devoted to reviewing the slides and answering general questions, and for the remainder of the time instructors will be available to answer students’ questions individually and to provide (limited) troubleshooting assistance.

• Expectations

COS 426 is a 400-level class. For students concentrating in Computer Science, this course will be marked as a senior departmental on their transcript. Accordingly, students should not only expect to be held to higher standards, but should also expect less hand-holding in general than they may find in 300-level courses and below.

In particular, students should not expect course staff to give them the answer to an assignment problem after enough pestering. Course staff are available to help students with their learning, not their grade. Here is a list of what instructors can help with:

Course staff are happy to help explain course concepts or general techniques that students may be confused about.

• e.g. “Could you please explain image convolution?”

Course staff are happy to clarify assignment specs, provided the clarification is not about an intentional ambiguity.

• e.g. “Should this filter rotate the image clockwise or counterclockwise?”

Course staff are happy to give the occasional starting hint (but no more) to put students on the right track for a certain problem.

• e.g. “The runtime of the brush filter should not exceed 4r^2 per center.”

Course staff are happy to answer questions about JavaScript syntax.

• e.g. “How can I iterate over entries in an Object?”
• Course staff will give modest debugging assistance only once students have demonstrated that they understand the solution to a problem at a high level (in other words, after students explain what they are trying to do, and that explanation is correct).

Unless a student has a JavaScript syntax question, instructors will not look at any code until the student has demonstrated that they understand the solution to the problem they need help with (see the last bullet point above). Second, unless it’s a syntax issue, instructors will not fix a student’s code for them. They will simply state what region of the code looks wrong. Also, if a student’s explanation is incorrect, instructors will not fix it for them. Course staff will either state what part of it is wrong, and / or ask a question to give the student something to think about.

• Course Grades

Final grades are based on six biweekly programming assignments (60%), one written exam (15%), a final programming project (20%), and course participation (5%). Throughout the semester, there will ample opportunities for extra credit and student participation. In particular, students are highly encouraged both to enter each assignment art contest, as well as to engage regularly with their peers on Ed .

• Written Exam

Only one exam is administered during this course. Currently, this exam is scheduled to be taken during the class time (either in-class or over Gradescope, TBA) on the Thursday of midterms week. The exam is closed-book; however, students are permitted to each bring an 8.5x11” double-sided cheat-sheet . The written exam covers all course material up through (and including) Week 5. Students may be tested on any and all graphics concepts touched on through lectures, readings, and assignments during this period. Examples of exams from previous offerings of this course will be posted; however, note that past exams may have covered different material. Students may also find the qualitative exercises available on the course website helpful when preparing for the exam, but they should expect more quantitative questions on the exam itself.

Although the six weeks of course material that follow the exam are not covered on any written test, it is still “tested” through strict no-collaboration questions that are introduced into assignment writeups following Fall Break. Effectively, these questions will serve as a second “take-home” exam spread throughout the later assignments. This is done in order alleviate the dependency of students’ final grades on their sole written exam grade, while also testing material without overburdening students with tedious and stressful examinations. Note that the grades for no-collaboration questions are incorporated into assignment grades rather than into exam grades.

• Programming Assignments

There are six biweekly programming assignments. Assignments are not weighted evenly. Assignments will be implemented mostly in JavaScript. Any computer and browser may be used for development, however students should ensure that their programs work on Chrome with the latest release of macOS, as this is the environment in which submissions are tested and graded.

Assignments are submitted via the Princeton CS Dropbox, also known as TigerFile. Students should look for the submission link in the description of each assignment, login with their Princeton netID, and then submit all applicable files by the posted deadline. Students may resubmit and unsubmit files as needed up until the submission deadline. Further alterations will result in the assignment being marked as late.

When submitting an assignment, all code, writeup, input images, output images, overlay images, etc., should be packed into a single folder titled “assignmentN” (where N is the assignment number — eg. , assignment0) and compressed. In the interest of preserving space, it is requested that all images are submitted in .jpg format.

• Final Project

The final project is a chance for students to build a system incorporating many of the ideas that have been covered in class, by implementing an interactive game. Projects should be done in groups of three or four (other team sizes are permitted with permission of an instructor).

Students are welcome to recycle code infrastructure provided for previous assignments, and they are also permitted to borrow content, ideas, or other code infrastructure from the web or elsewhere. However, teams should be very careful to distinguish which parts they contributed to directly, and which other parts are loaned from elsewhere. Moreover, while it is ok to use common libraries/infrastructure, they should not dwarf students’ own code in terms of their role in the project. In particular, projects should not build on top of a highly polished and complete game engine like Unity.

• Late Policy

Assignments are due at 11:55PM on their posted due dates, where submission time is determined by the file date of the file upload. Following a very brief grace period (which students should confirm with an instructor beforehand), one minute late is the same as one day late. Note that if any part of an assignment is submitted late, the entire assignment will be marked late. To submit an assignment late, remove all uploads from the online submission system, since instructors will grade partial submissions as-is (whereas no submissions are marked late). Note that work cannot be accepted after Dean’s Date without a Dean’s recommendation.

Late assignments are marked down 1/4 of the full grade per day or partial day late. This said, students may elect to waive up to four days of late penalties . We will not apply late days automatically in this course since the assignments are not weighted evenly. Therefore, if students would like to apply late days to a submitted assignment, please indicate at the top of the write-up . Additional late penalties will be waived only in the case of unforeseeable circumstances like medical emergencies, as documented by a student’s Dean or Director of Studies. Note that late days cannot be used for the final project as it is due on Dean’s Date.

Students who feel they have been incorrectly graded may write a short private Ed post describing the potential grading mistake. All regrade requests must be posted within two weeks of when the potential grading error was made.

• Collaboration Policy

Programming is an individual creative process much like composition. Students must reach their own understanding of the problem and discover a path to its solution. During this time, discussions among students in this course about the assignments is not only permitted but encouraged . Moreover, those who find they benefit from bouncing ideas off of their peers are encouraged to work in pairs .

Note that this is somewhat more relaxed than the collaboration policies of COS 126, COS 226, COS 217, etc., in the sense the conceptual components (ideation, brain-storming, understanding, problem-solving) of all assignments are partnered, even though programming components of assignments are still individual. This relaxed policy does not mean pairs are allowed share all their code with one another. Here is an executive summary:

• Individual Solutions

Students must individually compose all of their own solutions. The term solutions refers to any of the products created when completing a programming assignment excluding the writeup file, such as source code (including comments), a personal understanding of all submitted work, and output images. It includes both finished and unfinished products, regardless of correctness or completeness.

• Students must never share their code with anyone (besides their current partner) who is taking COS 426 now or who might take COS 426 in the future. Note that sharing output artwork with others is not only permitted but encouraged, so long as doing so does not expose solution specifics.
• Students must never receive or view someone else’s solutions to a programming assignment (or variant of an assignment), besides that of their current partner.
• Students must never view someone else’s writeup, including that of their current partner.

All the rules above continue to apply after assignments are graded and after the end of the semester.

• Collaboration with Course Staff

Students are welcome to discuss their solutions with course staff members during the precept problem sessions, in office hours, and via private Ed posts.

• Collaboration with Partners

Students may show their partial or complete solution to another student, and they may examine their solutions. However, all submitted code must be fully understood and more specifically typed into the computer by student submitting the assignment. If a student sees and understands another student’s solution (perhaps because they are working as a pair) then they should take a minute to think about it and then type their own version of the solution.

For each assignment, students must specifically state in their writeup file the names of any individuals with whom they collaborated, or from whom they received help, and the nature of the help that they received. This includes help from friends, the internet, classmates, and course staff members, among others.

• Collaboration with Classmates

Students are encouraged to discuss common concerns with classmates either in private or publicly in the Ed course forum. These discussions must be kept at a general level, without exposing their solutions.

• Concerning Electronic Communication

If a student has a question or comment that will be helpful to other students, and they need not reveal any parts of their work to express the question or comment properly, then they should post it to the course’s Ed page. One of the course’s instructors will reply as soon as possible. Instructors also welcome replies from other students and may “endorse” a student’s response instead of composing an instructor’s response.

If a student has a question or comment that will not be helpful to other students, or if they must reveal parts of their work to express their question or comment adequately, then they should post it privately on Ed .

Students should not, under any circumstances, share code in digital form!

Please do not publish solutions to programming assignments in a way that could compromise their utility as pedagogical tools. For example, do not make them available on a publicly accessible web page, such as GitHub. At Princeton, this is a violation of the basic Rights, Rules, Responsibilities of members of the University community.

Plagiarism and abetting plagiarism are serious academic infractions. Programming is a creative work and the academic regulations that apply to plagiarizing prose also apply to plagiarizing code. Princeton’s Rights, Rules, Responsibilities defines plagiarism as “the use of any outside source without proper acknowledgment.” It ranges from “verbatim copying” (e.g., cutting-and-pasting code) to “thorough paraphrasing” (e.g., changing variable names or rearranging code).

• Copying from a Partner

The more lenient collaboration policy for this course is a privilege; it is founded in the trust between students and instructors. If students are caught breaking this trust by violating the collaboration policy, they risk having this policy revoked for the entire class.

• Outside Sources & Citations

Students are only permitted to copy or adapt that is not theirs if it comes from the course materials (i.e., the course textbook, programming assignment specifications, lecture slides, precept slides, etc.). When students use outside sources, they must cite any code that they copy or adapt (with the exception of code that is included in the assignment starter files).

• Plagiarism Penalties

We refer alleged academic violations (including plagiarism and abetting plagiarism) to the Committee on Discipline . If found responsible, the typical penalty is an F as a course grade plus whatever penalty that the CoD imposes. (The typical CoD penalty for plagiarism is suspension from the University.) Violators of course policies that are not adjudicated by the CoD will receive penalties based on the severity of the violation, ranging from a warning (for violations that are both unintentional and innocuous) to an F in the course (for violations that are both intentional and serious).

• Acknowledgements

The COS 426 course staff would like to thank former COS 426 undergraduate and two-time TA Reilly Bova ’20 for creating this beautiful website and revising all the assignment specifications. We would also like to thank William Sweeney ’20 and Reilly Bova together for rewriting the precept slides and compiling supplementary content for the course.