Computer graphics II - labs (2018/2019)

Running tasks

022. 360°/180° equirectangular camera (deadline 21. 4. 2019) – 18 to 30 points

Ray-generator (ICamera) for panoramatic 360°/180° equirectangular camera, demo scene, upload panorama to FB/Google.

021. Layered reflectance model Weidlich-Wilkie (deadline 12. 5. 2019) – 28+ points

Implementation of the Weidlich-Wilkie reflectance model. Include material definition class and a demo scene.

062. RT animation with panoramic camera (deadline 22. 5. 2019) – 20+ points

Animated panormic camera, optional RT scene animation, optional animation script format. Making of video file, uploading to YouTube..

089. Efficient sphereflake for RT (deadline 9. 6. 2019) – 25+ points

Fractal object called "sphereflake", speeding up the computing of intersections.

097. Orange peel (deadline 30. 6. 2019) - 28+ points

Noise function used for orange peel imitation (bump-texture).

117. Hashing for noise generators (deadline 30. 6. 2019) – 22+ bodů

Hash functions are used in deterministic noise function generators. System for hash function testing (visualization in 2D).

Planned tasks

Tasks from the past (some of them are in Czech)

022. Alternative camera (deadline 16. 4. 2018) – 18 to 26 points

Ray generator for ray-based rendering methods. Implementation of a new camera (panoramic, fish-eye, ..) + demo scene.

061. RT scene design (deadline 1. 7. 2018) – 6 to 25 points

Design of an interesting 3D scene for Ray-tracing using the CSharpScript format.

062. RT scene animation (deadline 20. 5. 2018) – 22+ points

RT scene animation, camera animation is possible (perhaps the one from 022) + demo animation script. Making of video file, uploading to YouTube..

063. Flame animation (deadline 29. 4. 2018) – 25+ points

Procedural 2D flame animation. Implementation of your own (deterministic) noise function.

072. 3D noise-based texture (deadline 13. 5. 2018) – 25+ points

Continuous 3D noise function + some 3D texture based on it (wood, marble, ...).

079. Implicit surface for RT (deadline 10. 6. 2018) – 25+ points

Implicit function-defined surface for ray-tracing + demo scene.

088. Depth of field camera (deadline 1. 7. 2018) – 20+ points

Depth of field simulation (real camera lens with true aperture) using distributed ray-tracing technique.

065. Efficient parametric surface for RT (deadline 1. 7. 2018) – 30+ points

General parametric surface (defined symbolically) for ray-tracing. Suitable acceleration technique.

Credit requirements

Students have to earn min 50 points, upper limit is 80 points (Intro CG: at least 16 points have to be from 3D graphics assignments).
Deadline for winter-term credit is 17. 2. 2019 !
Deadline for summer-term credit is 30. 6. 2019 !

Credit points will be added to examination result (max 100 points) and the final grade will be determined using the following Grading Table:
150+ points A (výborně)
130 to 149 points B (velmi dobře)
110 to 129 points C (dobře)
less than 110 points F (nevyhověl(a))

How to earn credit points

A. assignments running through the whole term (implemented in C#)

Assignments are given in the labs (practicals), one assignment will be given in each lab. Students will have at least two weeks to deliver the assignments. Number of points awarded for a solution depends on the difficulty, solution quality, robustness, and elegance. Additional bonus points can be given, e.g. in case of a contest.

B. transfer from previous year

90% of last-year points could be transferred from the previous year (upon explicit student's request via email).


Some assignments have a well-defined quantitative criterion for solution comparison, based on which one can assemble a chart of best solutions. Such tasks will be marked as "CONTEST" and there will be a public chart displaying the best achieved results. In case the assignment is handed in by at least 10 students/teams, the three best solutions will obtain a premium of 10, 6, and 3 pts, respectively. (In case the solution was done in a team, all its members get the premium.) Only solutions submitted before the deadline are allowed to enter the contest!


Since grading of the assignments is very time consuming, your are kindly requested to follow several simple rules:
  • Mail messages have to be sent from an e-mail identity where your civil first name and surname can be easily determined.
    (Use something like "Malcolm Reynolds" <>.)
  • One message = one solution. If you want to ask an additional question or send a complaint, use a different email message!
  • Message subject has to contain the class code (NPGR003) and assignment ID number (a three-digit decimal number). Everything else is optional.
  • You absolutely must follow rules for source-file naming. There is a clear definition on each assignment's web page. Don't forget to write your name into a comment on the first line of the source file!
  • Do not send any unwanted extra files (there are exceptions but they are quite rare)
  • Never send huge mail attachments! If you want to send an image (demonstration of a good/bad case, input picture, etc.), use low resolution, or send an URL to, say, gyazo. Large files (e.g. videos) should be uploaded to a file sharing site (Dropbox, Google drive, OneDrive, etc.) and you will send the file URL in the email instead.
  • TEST functionality of your code. When grading, the code could be run in conditions slightly different from the obvious ones. If it fails, points go down. So make sure to produce robust code! Handle all (even weird) input conditions well.
  • Sometimes we will include special comments into source files to mark places where your code/changes should go. Please don't feel restricted by those comments. You can insert any variable/support class/data structure as long as it stays in the source file declared for consignment. Don't add more source files to the task project - they will be disregarded during the grading (and therefore you will not receive any points, because the program will probably not compile).

Submission of assignment solutions

Simply attach the requested source code to a mail message. Uncompressed, unecrypted, follow rules declared earlier (message subject, source file naming)!

Penalty for late submission

There is a penalty of 1 point for every day of delay after an assignment deadline.

Lab schedule

See Thu 15:40 SW2 (ground floor)
One English group every other week starting on 28 February 2019.

Copyright (C) 2000-2019 J.Pelikán, last change: 2019-05-16 18:31:56 +0200 (Thu, 16 May 2019)