Class Project

The following is a more detailed description of the project timeline and requirements:

Now: Topic Selection

Start thinking about what kinds of projects interest you and with whom you might like to collaborate. I suggest taking a look at the course schedule and talking with other students about mutual areas of interest. You might also check out the suggested project ideas in the blackboard system (Left Menu, Course Documents=>Suggested Project Ideas). If you would like me to help you find a project that fits your interests, please let me know.

9/15 Tuesday: Pre-Proposal Due (11:59 PM) 

Each group will submit a 2 page proposal describing the research project that you plan to work on. I expect to see sections on:
Please use the blackboard system (link on the course front page) to upload your project proposal. Each proposal should begin with a title. Each proposal should be single-spaced, with a single column and 12pt font, and have at least 1 inch margins. Submissions not in this format will not be reviewed. (This is to model program committees for conferences and workshops, which have the option to automatically reject papers if they do not comply with the submission guidelines).

9/29 Tuesday: Proposal Due (11:59 PM) 

Each group will submit a 3 page proposal describing the research project that you plan to work on. I expect to see sections on:
Please use the blackboard system (link on the course front page) to upload your project proposal. This proposal is a refined version of your pre-proposal.

10/6 Tuesday: One-on-One Meeting during Office Hour (2:00 PM)

Bring a short progress report (max 1 page). The progress report should explicitly address the milestones established in your original proposal, discuss which milestones you have met, and propose a new set of milestones if it appears that your original milestones are no longer appropriate.  Be ready to answer questions about what you've been working on, where you are stuck, what kind of preliminary results you have, what you plan to work on, etc.  This meeting should last about 10 minutes.

If you cannot come to this office hour, you have to schedule an appointment one week in advance.

10/20 Tuesday: Midpoint Review (11:59 PM)

Each group should submit a midpoint progress report (max 6 pages) to the blackboard system. This progress report should detail what you have accomplished so far since your last checkpoint. List all technical challenges if you are stuck in making progress.  

In your progress reports, you should reflect on what you have accomplished and draw preliminary conclusions from your results. If appropriate, you should also explicitly state any additional experiments or evaluations you may need to perform in order to strengthen your preliminary conclusions or answer open questions left by your preliminary conclusions. I expect to see sections on:
Here is a grading guideline for a midpoint review report (pdf).

11/3 Tuesday: One-on-One Meeting during Office Hour (2:00 PM)

Bring a short progress report (max 1 page). The progress report should explicitly address the milestones established in your original proposal, discuss which milestones you have met, and propose a new set of milestones if it appears that your original milestones are no longer appropriate.  Be ready to answer questions about what you've been working on, where you are stuck, what kind of preliminary results you have, what you plan to work on, etc. This meeting should last about 10 minutes.  

If you cannot come to this office hour, you have to schedule an appointment one week in advance.

11/17 Tuesday: Draft Report (11:59 PM)

Each group should submit a draft of their written report. The formatting of the draft report should match that of a final report. (See below for what a final report should look like.) The draft should be uploaded to the blackboard system.
It's OK if you haven't completed your research by now. See the next bullet for why you're turning in a draft two weeks before the final report is due. Your draft should clearly specify what you plan to do over the next two weeks. Your draft report will not be graded, but it will be reviewed by your classmates.

11/23 Monday: Peer Reviews Due (11:59 PM)

We will distribute your drafts to other students in the class, with the goal of simulating a mini program committee review process. This means you will also get comments from your peers. Consequently, you will all have the opportunity to read and review drafts from other groups. This process can be very educational unto itself, much akin to a miniature "program committee meeting."

You will be expected to read the draft reports that I give you (at most two) and write detailed reviews of those papers. You are to upload those reviews to the blackboard system by the above-specified deadline. The reviews you write should be anonymous (i.e., not include your name or other identifying information).

I will then collect those reviews and send them to the authors of the relevant reports. There are several reasons we're doing this, but the main goals are to (1) help you (as reviewers) gain more experience in evaluating in-progress (as opposed to completed) research and (2) help everyone improve the quality of their final written report.

11/30 Monday: Final Report, Electronic Presentation, and Implementation Zip File with Manual Due (11:59 PM)
 
Each group will submit a written report (max 10 pages), as well as a slide deck, to the blackboard system. Please submit the report and the slide deck as separate PDF files. You may include an appendix beyond 10 pages, but your paper must be intelligible without it. Submissions not in the ACM format will not be reviewed (this is to model program committees for conferences and workshops, which have the option to automatically reject papers if they do not comply with the submission guidelines).

Your report should be structured like a conference paper, meaning that your report should contain:
If you are doing a project that involves implementation, you must submit your souce code in zip file. This zip file must include test cases and manual in addition to source code. Your manual must describe how to run and test your code and must describe how you achieve empirical results described in your final report.

Here is a grading guideline for a final project report (pdf).

12/1 - 12/3: Presentations during Regular Classes

Each group will give a short presentation of their work during the final exam period. All group members should participate in the presentation. The length of the presentations will depend on the number of projects in the course, but I anticipate that each presentation will be 20 minutes long, and certainly no longer than 30 minutes.