Projects
Teams
Project pages will be available here later.
Rules
- The project has to be executed in groups of 2-3 people.
- The project gives you 30 points. You lose these points by missing deadlines.
- The project consists of
- A piece of (working) software.
- A short written report (in your project page) describing the topic, the tools, and methods used, mentioning the main complications and contributions. Including a 1-2 min video of the result.
- Discussion about the project with one of the instructors.
- A short (10 min) demo presentation.
- The project code must be hosted openly in a repository (we recommend Github or GitLab) and preferably as open source. Meaningful contribution from all team members needs to show in the repo log.
- Exceptions to the rules are possible via personal requests. Eg, if you really think you need 4 people on the team, come and explain why, presenting your plan and preliminary task list.
- To help you manage your project, feel free to use a project management tool of your choice, for example Codecks.
Deadlines
All deadlines are hard. You may miss them, but you pay with points.
- Oct 15. Registering Your Idea. Write down in CGLearn your initial project idea for others to join. Do not miss this deadline, otherwise you risk not getting to a valid team by Oct 24.
- Oct 22. Forming the Team. By this date, the team must be formed, and the project topic chosen in CGLearn.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Nov 12. Initial Progress. By this date, the team should be able to demonstrate something beyond "Hello World" that can be compiled/launched. At this stage, all your team members must have started working together and produced a proof of concept result. At least 500 LOC (or equivalent). 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 illustrated description of your project.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Dec 10. Coach Meeting. During the first half of December, the entire team needs to meet with one of the instructors and discuss your issues. Instructors will assume to see a 2/3 completed project from you and then 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.
- TBA. Final Release. By this date, the team should submit (make available from the project page) the project's final release. The release should include a short report written on your project page. You also need to add a small video that demonstrates your achieved result.
- Every day missed past the deadline: -2 pts.
- TBA. Project Demonstration. All members of the team must be present during the presentation.
- Not presenting your project results in the total project score of 0 pts for you.
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. We will discuss your registered ideas in the recap lecture.
Possible ideas
- A game with a sufficient graphical component.
- A created 3D scene, environment, objects (CGI, art).
- An interactive data visualization or simulation.
- Some interesting procedural generation approach.
- Here are some lists for ideas:
- Three.js - Showcase of things done with Three.js,
- Paul's Projects - Graphics algorithms implemented,
- CG Meetup Gallery - Beautiful short renders,
- The Graphics Codex Projects - More graphics algorithms implemented,
- Spore Prototypes - Procedural generation before there was Spore,
- Chrome Experiments - Cool stuff done on the web.
- Here are the projects from previous times: 2023, Fall; 2020, Fall; 2019, Fall; Fall 2018;
- Notable student projects