Project

General

Data and Resources

• Computer Vision Project [README] [folder to data]
• Natural Language Text Project [README] [folder to data]
• Audio Project [README] [folder to data]

Project Proposal

• Projects proposals are due on November 22.
• Please follow the project description in the domain you chose, and describe in some details what your technical plans are.
• The project has to include some reading. This is your chance to start reading some relevant paper(s). In your proposal, identfiy which technical direction you plan to take by referring to (a) paper(s) that you intend to follow or extend in the course of your project. Include citations in your proposal (do it in a way it is done in scientific articles.)
• The project proposal should clearly state, in a single page that is formatted like a paper (with appropriately listed references), the objective of the project, how you intend to go about it, reading list, and, in case relevant, what you have already done. Naturally, it should have a title and include the names of the participants/authors.
• Originality is not mandatory but is encouraged.
• Try to make it interesting!

Progress Reports

This is a short (1 page) report in which you briefly describe your progress so far. Decisions you have made on how to go about your project; papers that you consulted and found relevant, your plan for the rest of the project, and problems you have encountered.

Project Presentation

In addition to the final paper, you will prepare a short (3-5 minutes) video for your project. Introduce and motivate your work, and describe the key technical contributions and results in a comprehensible and visually appealing way. Please upload your videos to your google drive (give access to the professor and TAs) and submit the link on Gradescope.

Final Report

Eventually, you will write a short paper (4-6 pages; 11 font; please use the style suggested here). The final report and the video are due on December 21 2020.

Below are guidelines on how to write up your report for the final project. These are only guidelines; you will need to adjust it to the problem you are investigating, but try to structure your report along these suggestions and make it look like an article. Please don't use the guidelines below as subtitles of your paper; these are just guidelines. Try to make it look like a published article.

1. Introduction: Motivate and abstractly describe the problem you are addressing and how you are addressing it. What is the problem? Why is it important? What is your approach? What is the goal of your paper? Provide a short discussion of how the problem and your approach fit into related work in the area. Summarize the basic results, conclusions and contributions that you will present.
2. Problem Definition and Algorithms
   • Task Definition: Introduce the model and/or problem you are studying and define the notation you are going to use. Precisely define the problem you are addressing (e.g., formally specify the inputs and outputs). Elaborate on why this is an interesting and important problem.
   • Algorithm(s) Definition: If you study learning algorithm(s) experimentally this is the place to present it. Describe in reasonable details the algorithm(s) you are using. A pseudo-code description of the algorithm you are using is often useful. Depending on the context, it may be useful to trace through a concrete example, showing how your algorithm processes this example.
   • Expectations: In case of an experimental study, discuss what you hope to achieve. How do you expect each algorithm to behave and why. Try to justify your hypothesis as rigorously as possible. Discuss how your expectations drive your experimental design.
3. Experimental Evaluation
• Methodology: What are the criteria you are using to evaluate your method? Describe the experimental methodology that you used. What is the training/test data that was used, and why is it realistic or interesting? What performance data did you collect and how are you presenting and analyzing it?
• Results: Present the quantitative results of your experiments. Compare to the literature (state-of-the-art, ideally) and to an sensible baseline method. Graphical data presentation such as graphs and histograms are often better than tables. What are the basic differences revealed in the data. Are they statistically significant?
• Discussion: Is your hypothesis supported? What conclusions do the results support about the strengths and weaknesses of your method compared to other methods? How can the results be explained in terms of the underlying properties of the algorithm and/or the data.
• Data Analysis: it is often useful to discuss error and/or analyze some test cases as a way to illustrate the problem, your method, the limitations, etc.
4. Theoretical Evaluation (when relevant): If you are writing a theoretical paper and/or a survey, this is the place for your analysis and contribution. Try to make it clear what parts of the work are presentation of known work, what is given a new look by your presentation and what is novel in your view of the problem.
5. Related Work: This part need not be exhaustive, but you need to know about some of the related work. Discuss the problem and method in the related work. How is your problem and method different? Why is your problem and method better?
6. Future Work (Only if relevant): What are the major shortcomings of your current method? For each shortcoming, propose additions or enhancements that would help overcome it.
7. Conclusion: Briefly summarize the important results and conclusions presented in the paper. What are the most important points illustrated by your work?