Projects
Teams
- WebGL audio visualizer - Karl-Aksel Puulmann and Raimond-Hendrik Tunnel
- Brain activity visualization - Anna Leontyeva, Dmytro Fishman and Ilya Kuzovkin
- Fluid dynamics - Erich Erstu and Siim Kallas
- Path tracer - Maarja Lepamets, Indrek Loolaid and Jaak Randmets
- Town growth simulation - Karl-Oskar Masing, Margus Luik and Janno Jõgeva.
- Procrastinatron Xtreme - Saad Usman Khan, Ilja Kromonov and Meelis Müür
- The subway game - Märt Bakhoff and Anne Mirjam Kraav
- Zombie boids - Ats Kurvet
Abandoned projects
- Dungeon (game) - Priit Metsik and Risto Saar
- Game Z - Kaisa Jürmann and Ivari Tölp
- Physically based shading - Ats Kurvet and Martin Loginov
- Solar System - Kira Lurich and Jonatan Raudsepp
Rules
- The project has to be executed in groups of 2-3 people.
- The project provides up to 30 points (i.e. makes up to 30% of the final grade). You lose points by missing deadlines.
- The project consists of
- A piece of (working) software,
- A short written report describing the topic, the tools and methods used, mentioning the main complications and contributions, etc. (preferably under 2 pages)
- A short (10 min) demo presentation.
- The project code must be hosted openly (I strongly suggest Github) and licensed as open source.
- Exceptions to the rules are possible via personal requests. E.g. if you really think you need 4 people on the team, come and explain why, presenting your plan and preliminary task list. You can also consider executing a research project (e.g. developing/evaluating an algorithm and producing a paper rather than a piece of software).
Deadlines
All deadlines are hard. You may miss them, but you pay with points.
- September 22. Forming the team. By this date (23:59 the latest) the team must be formed and project topic chosen. A brief topic description should be e-mailed to kt@ut.ee.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- October 20. Initial progress. By this date the team should be able to demonstrate something beyond "Hello World", that can be compiled / launched. At least 500 LOC. Code + compilation / launching guide should be sent to the same e-mail.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- December 11. Final release. By this date the team should submit the final release of the project.
- Every day missed past the deadline: -2 pts.
- December 16. Written report. Make sure the report is accessible from your project's page on the course website.
- Every day missed past the deadline: -2 pts.
- December 18. Project demonstration.
- Not presenting a demo results in the overall score of 0pt for the project.
Potential topics
You are free to choose the topic on your own, as long as the resulting project is exciting enough for you, and requires at least 1.5 full working weeks (around 60 hrs) per person to complete.
Possible ideas:
- A game (here are some old yet still relevant examples).
- A 3D demo.
- An interactive data visualization or simulation (think filebrowsers, the web, physics, chemistry, neuroscience, bioinformatics, geodata ...)
- A screensaver, etc.
- Here is the list of projects from the last time the course was held (in Estonian). Note, however, that the choice of potential platforms, ready-made libraries, models and data sources for doing real-time graphics has expanded immensely since then.