Project
In addition to lectures and presentations in class, there is also a lab, PF-3342, corresponding to the class. For the lab, the students will work individually on a project, choosing one of the following topics:
- The implementation and/or application of an AI technique published at an appropriate conference or workshop, like AIIDE, CIG, PCG or EXAG. Examples for suitable papers are:
- Procedural Generation of Roads
- Addressing the Elephant in the Room: Opinionated Virtual Characters
- Desire Path-Inspired Procedural Placement of Coins in a Platformer Game
- Poetic sound similarity vectors using phonetic features
- Social Simulation for Social Justice
- ProcDefense — A Game Framework for Procedural Player Skill Training
- POMCP with Human Preferences in Settlers of Catan
- Exhaustive and Semi-Exhaustive Procedural Content Generation
- Tarot-based narrative generation
- Generating Levels That Teach Mechanics
- A semantic approach to patch-based procedural generationof urban road networks
- TaleSpin: An Interactive Program that Writes Stories
- Glaive: A State-Space Narrative PlannerSupporting Intentionality and Conflict
-
The implementation of an AI agent for a game of the student’s choosing. It is advisable to choose a game where an open source implementation is already available (like Quake 3), or can be created without too much effort (like Kingdom Builder).
- The implementation of an AI agent for a competition held at AIIDE or CoG, for example:
- The implementation of a procedural content generator. This project type is also expected to use techniques from published work, but focuses more on developing something that can create a variety of outputs. The instructor will provide several suggestions, using Kate Compton’s Generominos
Students are also free to propose their own ideas, as long as they are related to AI in digital entertainment. The project consists of two main deliverables:
- A project proposal (2-4 pages), with a summary of the necessary background information, the problem the student is proposing to work on and the evaluation criteria. Due 31/3.
- A prototype/milestone submission, demonstrating the feasibility of the project, and a short description of which parts already work/are still missing. Due 3/6.
- The final delivery, consisting of all code necessary to run the project, as well as a 2-6 page report that contains the technical contribution of the student as well as an illustration of the result, compared against the evaluation criteria described in the proposal. Due 4/7.