Technical Report

After you have given the best presentation you can, write a technical report about your project (you may want to add detail in areas of your presentation that got questions or gather additional data).

The quality and contents of your reports can cause Adam to re-evaluate his score of your final presentation (if the written detail seems to retroactively improve the Challenge/Achievement/Clarity). 

The report should be organized like a computer science conference paper with length ranging from about 4-6 pages of main content (not counting optional appendices). It is not necessary to use a specific technical document layout (e.g. the ACM conference format) -- a pdf exported from Google Docs with nice section headers would be reasonable.

Things that should be included:

- A descriptive title that will make sense to AI/Games researchers outside of the class

- An authors list including all team members (submit one report per team)

- An introduction to the project that sketches what value you believe the project has for what stakeholders and outlines the problem setting and or approach. The introduction section should claim to make at least one technical contribution, however small. It's okay to write it out explicitly: "This paper contributes: {bulleted list}" (Inspiration: https://plg.uwaterloo.ca/~migod/research/beckOOPSLA.html Links to an external site.)

- A related work section that explains how your project relates to the closest academic and/or industrial projects (formal citations are not necessary if you'd prefer to simply put hyperlinks in footnotes)

- Some number of content sections that explain the project in more depth, using screenshots or diagrams from your presentation where appropriate. Recycle material from your presentation where possible. It is not necessary that someone be able to recreate your project from the document, but we should be able to be reminded of the Challenge/Achievement/Clarity of your presentation from what you include in these sections.

- A useful conclusion section, however brief.

- Optional: Appendices containing extra code samples, screenshots, or other material that you are either particularly proud of or think might add some clarity. Because there is no official page limit for the report, you can have very lengthy appendices. Don't spend too much time on this section; start your Spring Break early