Inspired by Ludwig Schmidt, Alec Jacobson and Colin Raffel, we will be discussing papers in the many-to-many role-playing format. Each session you will be assigned to a group with one of the following roles:

• Summarizer. This team will be responsible for providing a short 8 minute summary of the paper and will be the first role to present. Create a presentation using google slides highlighting the motivation for the paper, as well as the key techniques and results. A suggestion for creating this would be to create slides for the major figures in the paper that communicate these and talk through them.


• Scientific peer reviewer (advocate). Imagine you are a reviewer for this paper and it is under submission to a top conference or journal. More specifically, you are a positive reviewer advocating that it should be published. Present the strengths of the paper and/or changes you think should be made before publication.


• Scientific peer reviewer (skeptic). Same as above but in this case focus on the weaknesses and criticisms of the paper.


• Researcher. Imagine you are a researcher in academia or industry reading this paper. Propose a follow up work or a potential application.

For each paper the summarizing team will have 8 min to present, the other groups will have 4 min each with time for questions and discussion after.

The goal of this project is to offer an open-ended opportunity to explore a technology in this domain of your choice. This can be anything from software to hardware depending on your background, expertise, and interests. We’ll go over some potential ideas in class but be creative! Please just make an effort to connect this to the concepts discussed in the course (e.g. discussing how the project might scale to limited hardware, power, etc). Group projects are acceptable, however, the scope of the project should be scaled based on the group size (if you have a larger group the project should be more substantial). Each group will present their project at the end of the quarter.

Project proposal (due 1/25)- The proposal should be a one to two page writeup of what you’d like to do. Please include the motivation, description of what you plan to build, and at least one experiment you plan to do to evaluate it. If you need any hardware to do this please include that as well with costs (and contact me). On 1/27 instead of class we’ll have brief zoom meetings to go over each of the proposals.