CS 175: Project in AI (in Minecraft) Spring 2017
◦ Approaches:
Use another level-two header called Approaches, In this section, describe both the baselines
and your proposed approach(es). Describe precisely what the advantages and disadvantages of each are,
for example, why one might be more accurate, need less data, take more time, overfit, and so on. Include
enough technical information to be able to (mostly) reproduce your project, in particular, use pseudocode
and equations as much as possible.
◦ Evaluation:
An important aspect of your project, as I’ve mentioned several times now, is evaluating your
project. Be clear and precise about describing the evaluation setup, for both quantitative and qualitative
results. Present the results to convince the reader that you have solved the problem, to whatever extent you
claim you have. Use plots, charts, tables, screenshots, figures, etc. as needed. I expect you will need at least
a few paragraphs to describe each type of evaluation that you perform.
◦ References:
Make a list of work you’re citing in your description above (starting with a level-two header).
This should include any papers you think are relevant, third-party source code you used, sources for any of
the images that you didn’t create, and any other websites/links you found useful.
A template for the final report is available here:
https://raw.githubusercontent.com/sameersingh/
gh-skeleton/master/docs/final.md
. Please make sure your headers of each section are formatted similar
to the template, but you’re free to organize each section using lower-level headers, i.e. 3 ( ### ) and 4 ( #### ).
2 Contributions, 40 points
A Contributions assignment will appear separately on canvas for you to describe you own contributions, your
teammates’ contributions, and evaluate yourself relative to your teammates. Keep in mind that if your project
didn’t work out, we’re already taking that into account in other sections; this one is primarily to evaluate how
much you put into the project.
◦ Your Contribution:
In the first part, describe your own contributions to the project as a list of things you
did, in no more that
250 words
(lesser the better). These can include things that maybe didn’t make into
the source code, for example you tried some feature but it didn’t work, or were responsible for the video, or
you read a lot of papers and taught your teammates about it. Also, give yourself a letter grade (F, C, B-, B,
B+, A-, A, A+) as to how well you think you did relative to your teammates, and the rest of the projects (as
you’ve seen so far), using the text above as justification. Needless to say, this will not be your grade, so it’s
more important be honest than try to inflate this.
◦ Teammates’ Contribution:
For each teammate, give them a letter grade (F, C, B-, B, B+, A-, A, A+) for how
much you think they contributed. Again, be fair; give them a higher grade than you if they did more work
than you, and avoid finding blame for why (if) the project didn’t come together. Also, justify your grade by
providing a list of their contributions, using a maximum of
100 words
for each teammate. This will not
directly be your teammates grade, but I want to make sure unfair contributions are evaluated appropriately.
It wouldn’t be a bad idea to make a list of your and your teammates contributions, and have a group meeting
to go through those, and make sure everyone is on the same page.
Project Final Submission UC Irvine 2/ 2