Final Project Report

Due Friday 5/11, 10pm

Your project report can be either styled as a research paper or as a blog post. Paper format reports are like research papers and will be 6-10 pages in length. Blog posts should have equivalent length, but may be more graphics heavy. Here's the example Blog from the "best practices" section: http://distill.pub/2016/augmented-rnns/ Links to an external site.

The goal of your report is to fill in all the details of your project, so that someone else could fully reproduce your results. There are different styles for writing research papers, and even more freedom in writing blog posts. We give some suggestions below on content to include. These items don't need to be separate sections, but your report should contain this content somewhere.

Problem Statement and Background

Give a clear and complete statement of the problem. Don't describe methods or tools yet. Where does the data come from, what are its characteristics?

Include informal success measures (e.g. accuracy on cross-validated data, without specifying ROC or precision/recall etc) that you planned to use.

Include background material as appropriate: who cares about this problem, what impact it has, what implications better solutions might have.

Included references to any related work you know about.

Approach

Start with data preparation. If you used an off-the-shelf dataset, you don't need to say much. But if you did any non-standard preparation, or if you spent any time iterating on your data prep., please describe it thoroughly.

Describe your baseline model. Give a graphical representation of it.

Describe your final model. Explain the evolutionary process to get to it. What other models did you try? What worked and what didnt?

Results

Give detailed results for baseline and final models. Make sure you're very clear about what dataset was used, how train/validate/test partitioning was done, what measures were used.

Explore surprises. Whenever a method didn't behave as expected, explore and try to figure out why.

Please use visualizations whenever possible. Include links to interactive visualizations if you built them.

Tools

Describe the tools that you used and the reasons for their choice. Justify them in terms of the problem itself and the methods you want to use.

Lessons Learned

Give a high-level summary of your results. Make sure you summarize your results at the beginning and also at the end of your report.  You can refer back to the "Results" section for elaborations. In particular emphasize any results that were surprising.

Team Contributions

This information must be in a section called Team Contributions at the end of your report. Please give a percentage breakdown of the effort from each team member, and what they worked on. Please discuss this within your team to make sure every member agrees with the breakdown.

Submission

Please submit your project report by Friday 10pm 5/11 using this link. You can upload your report, or include a link to your post.

Project Archival Preferences

We would like to publicly archive the projects, but we need your permission. Please specify your group's preference with this link by Friday 5/11.