Jan30: Project email proposal due Send an informal text-only email
to the instructor to list your group members (if any), to briefly describe your
topic selection, and in a few paragraphs describe your approach. Be clear on
what infrastructure you will use/need. The goal is that the proposal should
make it clear what you plan to do and how. You may *additionally* include a pdf
if you must also include pictures/figures. Some/most of you may want/need to
discuss your ideas with the instructor for more details, right after class is a
good time to do so.
Feb13: Project written proposal due Email a 1-page pdf proposal to
the instructor. This should contain an introduction, description of
infrastructure to be used, a description of your implementation/evaluation plan
(ideally this is prioritized a list of things you will do, such that you may
not do the whole list if time does not allow), and a summary of what you hope
to learn/find.
Mar13: Project interim presentation A 5 minute presentation describing
the basic idea of your project and the progress made so far, must include some
preliminary result.
Apr10: Project poster session (tentative) You will create a 6-9
slide (page) "poster" (8.5x11 printouts is fine), and in class this day we will
present all posters for each other throughout the class period.
Apr23: Project final written reports due The final report will
be styled after the conference papers that are included in the class reading
list. With the final report you should also provide a tarball (or a pointer to
a tarball) of the code that you developed, plus a README describing the key
contents. An email is sufficient.