News

Second reading assignment

Written on 07.11.25 by Pascal Grittmann

The PDF for the second reading assignment has been uploaded to the course materials: https://cms.sic.saarland/cg_25/dl/16/02-Veach-Chapter3-Radiometry.pdf

You can also find a PDF of the full thesis here: https://graphics.stanford.edu/papers/veach_thesis/thesis.pdf 

Exam dates

Written on 24.10.25 by Pascal Grittmann

The final exam will take place on Tuesday, 17 February 2026 in the Günter Hotz lecture hall (E2 2) from 14:00 to 16:00

The re-exam will be on Tuesday, 17 March 2026 in E1 3 HS002, also from 14:00 to 16:00

You can also find these times in the calendar on CMS (Read more

The final exam will take place on Tuesday, 17 February 2026 in the Günter Hotz lecture hall (E2 2) from 14:00 to 16:00

The re-exam will be on Tuesday, 17 March 2026 in E1 3 HS002, also from 14:00 to 16:00

You can also find these times in the calendar on CMS (https://cms.sic.saarland/cg_25/termine/calendar/index)

Reading assignment

Written on 24.10.25 by Pascal Grittmann

The first reading assignment has been uploaded (https://cms.sic.saarland/cg_25/materials/)

GitLab Account

Written on 21.10.25 by Pascal Grittmann

To access the git repository, you need to

  1. Log in once on https://gitlab.cs.uni-saarland.de/ with your SIC account (before the first login, the account on GitLab does not exist and we cannot give you access)
  2. Provide your account name on your personal status page 

Tutorial Assignment Released

Written on 20.10.25 by Lukas Auer

Dear Students,

We have just released the tutorial slot assignments.

Next Steps:

  • Registration for submission is now open and can be found under the "Personal Status" tab.
  • The deadline for team creation is October 26th at 23:35.
  • Make sure that you and your teammate are in the same… Read more

Dear Students,

We have just released the tutorial slot assignments.

Next Steps:

  • Registration for submission is now open and can be found under the "Personal Status" tab.
  • The deadline for team creation is October 26th at 23:35.
  • Make sure that you and your teammate are in the same tutorial slot.
  • To find a partner, you can consult the forum, where a dedicated thread already exists.

Written on 17.10.25 by Pascal Grittmann

Welcome to the course :) There are a few things you need to do for a smooth start into the semester.

On your personal status page in CMS, please:

  1. Fill in your tutorial preferences (Deadline on Sunday, 19.10.)
  2. Provide your SIC account name for git repo access (if you are unsure about the… Read more

Welcome to the course :) There are a few things you need to do for a smooth start into the semester.

On your personal status page in CMS, please:

  1. Fill in your tutorial preferences (Deadline on Sunday, 19.10.)
  2. Provide your SIC account name for git repo access (if you are unsure about the account, check https://sam.sic.saarland/)

Regarding tutorials:

  • Next week, there will be a tutorial, in your assigned slot, to guide you through the process of setting up the framework for the practical assignments. 
  • Afterwards, the tutorial slot will be used for the mandatory code interviews (during lecture weeks only; there are no tutorials during office hour weeks)
  • If you already have a favorite team partner: Both students in a team must be in the same tutorial, so please try to provide the same preferences. If you end up assigned to different tutorials, get in touch with us and we'll see what we can do.

Finally, if you have changed your mind about taking the course, you can unregister (personal status page on CMS) to avoid getting spammed with notifications and requests for missing info.

Show all

Computer Graphics

This course provides a hands-on introduction to the fundamentals of computer graphics. You will learn concepts including ray tracing, texturing, and camera models. In the practical assignments, you will apply this knowledge to build your own ray tracer. The course culminates in a rendering competition, where students model a 3D scene and render it with their own renderer, competing to see who can make best artistic use of the tools they have built.

The first lecture is on Thursday, 16.10. at 08:30 in E1 3 HS 001

Pre-requisites

  • Programming experience (assignments use C++)
  • Basic knowledge of linear algebra and analysis

We will be using the university's GitLab (https://gitlab.cs.uni-saarland.de/) for the practical assignments.
A SIC account (https://sam.sic.saarland) is mandatory for that, so please make sure you can log into yours.

Format

The first half of the course (until the winter break) follows a non-standard format:

  • The course is split into blocks, each lasting two weeks
  • Each block comprises
    •   two lectures (Monday and Thursday of the first week),
    •   a practical assignment (graded),
    •   a reading assignment, and
    •   a mini-test (mandatory but ungraded)
  • During the first week of each block:
    •   Monday, 10:15: lecture, practical assignments released
    •   Thursday, 08:30: lecture, reading assignment released
    •   Throughout the week: code interviews with your tutor about the previous assignment (mandatory)
  • During the second week of each block:
    •   Monday, 10:15: mini-test, solutions for test and previous assignment are discussed, office hour
    •   Thursday, 08:30: office hour
    •   Sunday, 23:59: practical assignment deadline

In the second half, starting January, there are lectures every Monday and Thursday and no assignments (you will be working on the project and rendering competition).

Precise dates can be found in the calendar here on CMS (Information/Timetable at the top).

Practical Assignments

Assignments are posted on CMS every second week during the first half of the course. Assignments are mandatory (every single one must be submitted) and part of the final grade.

We allow students to submit in groups of two. These groups must be fixed before submitting the first assignment and cannot be changed later on.

Both team members are expected to fully understand all code. If, during code interviews, the tutor repeatedly notices that a student does not understand the submitted solution, further measures might be taken to ensure fair grading.

Mini-tests

Mandatory mini-tests are held every second Monday in the lecture hall. While these tests are not graded, students must submit a solution for every test to be admitted to the exam.
In justified cases, we allow students to submit test solutions via email to their tutor instead. Justifications include medical reasons and schedule conflicts. Students must notify their tutor and provide proof at least one week before the test.

Project and rendering competition

After the last practical assignment, you will work on the project and rendering competition. Both are mandatory and graded.

In the project, you extend your renderer by additional features of your choice. By implementing more features than required, you can obtain bonus points (with a soft-max limit). Ideally, you choose your features such that they benefit your rendering competition entry.

With the rendering competition, you will show that not only do you know how to write a renderer, but also how to use it to render an appealing, original scene. The competition will be graded based on completeness (creation of an original scene, rendering it, presentation via a webpage that describes the idea and methodology) and bonus points will be awarded to the top-ranking submissions (based on artistic merit as judged by a jury).

Grading

The final grade is computed as follows:

  •  20% Project and rendering competition (minimum 50% to pass)
  •  30% Assignments (minimum 50% to pass)
  •  50% Final exam (minimum 50% to pass)

Bonus points: By implementing additional features or winning the competition, your points for the project can exceed 100%. These additional points are included in the total prior to weighting, i.e., the formula for the final grade is:

final = 0.2 * (project + bonus) + 0.3 * assignment + 0.5 * exam

 

Privacy Policy | Legal Notice
If you encounter technical problems, please contact the administrators.