Projects
Teams
- Chicken Ralley – Sercan Altundas, Shalva Avanashvili
- Visualization of Caustics – Aleksandra Leesment, Cardo Kambla
- Audio Visualizer + GPU Particles – Andres Nirk, Madis Janno, Heiti Ehrpais
- Minecraft Rip-Off – Sander Pärn, Markus Saarniit, Ott Saar
- Procedural and Dynamic Meshes – Ott Adermann, Jaagup Kirme, Ergo Nigola
- Visualization of a Classroom – Aleksander Nikolajev, Andrei Voitenko
- Shooting Simulator – Kaius Loos, Kristjan Vedler, Sander Lepik
- Volumetric Fire 🔥 – Jaagup Kuhi, Siim Raudsepp, Andri Poolakese
- Designing Own Planet – Andreas Baum, Agu-Art Annuk
- City Traffic Simulator – Robert Sepp, Miron Storožev, Janar Saks
- Geographical Map of Estonia – Tõnis Lepik, Karl Vaba
- Brain Data Visualization – Simo Pähk (superv. Ilya Kuzovkin)
- VR Mesh Sculpting Tool – Aadam Kaivo, Tõnis Ojandu
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)
- Discussion about the project with one of the instructors
- A short (10 min) demo presentation.
- The project code must be hosted openly (I strongly suggest Github) and preferably 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.
- Oct 22. Registering your idea. Write down here your initial project idea for others to join. Do not miss this deadline, otherwise you risk not getting to a valid team by Oct 29.
- Oct 29. Forming the team. By this date (23:59 the latest) the team must be formed and project topic chosen. The corresponding information should be available here.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Nov 19. 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 available in the repository. Also your project's course page should have a link to the repository and a brief description.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Dec 17. Coach Meeting. During the first half of December the entire team needs to meet with one of the instructors and discuss the issues they are having. Instructors will assume to see a 2/3 completed project from you then in order to have a meaningful discussion. Team-specific meetings will be scheduled in November.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Jan 7. Final release. By this date the team should submit (make available from the project page) the final release of the project. The release should include a short (1-2 page) report, that can be written on the project page, in the git's readme.md file, or made otherwise easily accessible. Also add a small video, which demonstrates your achieved result.
- Every day missed past the deadline: -2 pts.
- Jan 9. (12:00 - 18:00, room 111). Project demonstration. All members of the team must be present during the presentation.
- Not presenting a demo results in the overall score of 0 pts 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 full working week (around 40 hrs) per person to complete. Naturally, it should be (at least in part) related to computer graphics.
Possible ideas
- A game with a sufficient graphical component (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 ...)
- Some interesting game mechanic idea (examples)
- Here are some lists for ideas: Paul's Projects, CG Meetup Forum Showcase, The Graphics Codex Projects
- Join a project from APT Game Generator group: projects.
- Here are the projects from the last times: 2016, Fall; 2015, Fall; 2015, Spring; 2013, Fall.
Topics with a distributed / parallel computing problem (can earn extra 10p)
Distributed and parallel computing systems allow for very high quality animations in interactive multiplayer games. Students interested in pursuing computer graphics projects that make use of distributed and parallel computing are welcome to talk to me to see if something suitable can be found. It is hoped to also create material that may be demonstrated at ISC 2015 , so use of openly available tools is highly appreciated, in particular OpenCL and OpenGL on CPUs and GPUs. - Benson
Possible topics here are:
- Efficient volume rendering algorithms and implementations for visualizing three dimensional fields
- Multiplayer car racing game using Blender and OpenFOAM -- the aim is to allow people to design their own racing car, then simulate the aerodynamics to give realistic handling that will allow others to predict their design. See for example: https://summerofhpc.prace-ri.eu/project-reports-2014-martin/
Contact Benson Muite (benson.muite@ut.ee) for more details and supervision of those topics.