Course Project
TL;DR for Deadlines
| # | Checkpoint | Deadline |
|---|---|---|
| 0 | Team registration / match request (for both A3 and project) | 02/10 |
| 1 | Abstract | 03/03 |
| 2 | Midpoint project report (2-3 pages) | 04/09 |
| 3 | Project presentation (duration TBD) | 04/28 and 04/30 |
| 4 | Final project report (6-8 pages) | 05/07 |
Overview
Please see **https://docs.google.com/document/d/1C8Dl6DX0_F5g3HDR-Gwr1fTmKGgscxzbU9AiUpvxV0k/edit?usp=sharing for logistics and reference topics.
Project FAQ
Using the same project for CS 288 and another class
While the projects can be related and use a shared codebase, you may not submit an identical project as another class project. If any part of the project is done for another course, please clearly indicate in the Contributions section of your report which part of the project was done for CS 288 and which part was not.
Using your ongoing research as your CS 288 project
This is allowed. In the Contributions section of your writeup, you should indicate this and describe which parts were done prior to the start of the course vs. which parts were done for the course. You will be evaluated on the parts that were done after the start of the course, i.e., you may not reuse a previously completed project.
Collaborating with people outside this course
This is allowed (e.g., your advisor and labmates might be involved in your ongoing research). In the Contributions section of your writeup, you should indicate this and describe which parts you were responsible for. If you are repurposing text or slides that were written by your collaborators, you should also declare this. You will be evaluated on the parts that you worked on.
Generative AI policy
See the course info page.