Final Project

Click here to see a collage of all student final projects


There will be one large final project in this course which accounts for 25% of the final grade and which will be done over roughly half of the course. The projects all span fun topics which should lead to some tangible deliverables at the end of the course. They must be done in groups. Each project is novel in some way, where novelty could be measured by the problem, the approach, or the accessibility of existing methods to non-experts. Project groups and topics will be determined about a third of the way through the course

Project Presentations / Documentation

Due to the larger class size this semester, it is simply not feasible for everyone to present their final projects during class time. Instead, students will be required to make videos summarizing their work. Talking over a powerpoint is fine, but this is also an opportunity to make a more visually polished result, possibly even with animations, which is appropriate given the nature of this course. Once the videos are completed, each student will be randomly assigned 3-4 videos from other groups in the course to watch and for which to provide critical feedback. This feedback will factor into the participation grade.
NOTE: I will of course also be watching each video carefully myself.
NOTE ALSO: This fabulous idea about video recorded presentations is adapted from one of my research collaborators Paul Bendich

No formal writeup will be required for the projects, but students will be expected to submit a brief document summarizing their accomplishments in bullet form, providing a summary of completed code, and providing directions to use the code

Grading Rubric

20%Initial project milestone: How close did you get to accomplishing the initial goals we set out?
45%Technical refinement: How much did the project mature over the time you worked on it? How close are you to the final goal that we had?
15%Narrated video: Graded for overall clarity, quality of figures/animations, and demonstration of what you did so that other students can understand it
10%Code/Documentation/Mini Report: In lieu of a formal final report, you will submit a brief summary of what you accomplished, along with code and directions on how to use it. You can think of this as an extended README. You will be graded on the quality of your code and documentation (how easy is it for someone who doesn't know your project to run your code or to get started replicating your results?).
You should also submit a single slide with a representative screenshot and some bullet points describing what you did for the class final project collage
10%Above and beyond: How much did you do to refine this project and to make it your own? Did you put any unique twists on it that weren't suggested by the instructor?

Project Topics

Below are a list of projects that students can choose from. Towards the beginning of the second unit of the course, groups will rank their top three choices, and the instructor will assign projects based on interest and the technical background of each group.
NOTE: There will likely be more than one group to working on the same project. In that case, some collaboration is expected between the groups getting through core issues. Otherwise, unique solutions are expected, or the groups should carve out different portions of the same problem