|
Projects can be done individually on in pairs.
- September 3: Send me email stating whom you will work with (or that you will work on the project alone), and describing the project in one or two paragraphs. This email counts for 10 percent of your project grade.
- September 17: Send me email with your project plan, describing in detail what you plan to do and how. Your plan should be in Adobe PDF (preferred) or MS Word, and should include a problem description, a brief discussion of relevant literature (1-5 papers), a description of your deliverables, a schedule of work, a discussion of possible pitfalls and difficulties, and workarounds for them. Typical length of a project plan is 2-4 single-spaced pages. This plan counts for 30 percent of your project grade.
- October 29: Send me email with a draft of your project report. This can be a PDF or MS Word file, or a URL. In the latter case, make sure that all your links work. I cannot grade what I cannot access. A typical project report is 5-10 pages of single-spaced text and figures. Good form (including grammar and proper citations) counts as well. The project report draft counts for 30 percent of your project grade.
- November 26: Send me email with your final project report in the same format as your report draft (includng good form and grammar!). What counts is not whether the project was successful, but how much you show that you learned from it. The main differences between the draft and final version of the project report is that the latter may incorporate my feedback based on your draft. The final project report counts for 30 percent of your project grade.
The following project examples are intended to give you an idea of the scope of a typical project. You may choose to do one of the examples, but coming up with your own ideas is preferable. Variations on the project examples below can be obtained by replacing, say, "image motion" with "stereo," and so forth.
- Write code that segments images by color or texture, and discuss what works and what does not.
- Implement or port an edge detector or a tracker onto an PDA or cell phone equipped with camera. This is tricky: check first that you can find an appropriate development tool for your phone's operating system. If you do this project, tell me where you find the necessary tools in your 9/17 project plan. You will also need to know or quickly learn the relevant programming language. Try to write something tiny before you commit to this type of project.
- Download existing code for tracking pedestrians and discuss its performance on a few video sequences acquired in the vision lab, or downloaded from the web.
- Find a shortcoming of an existing image motion algorithm and attempt to fix it.
- Use your cell phone camera or other camera to create test video. Use the video to evaluate a point-feature tracker you download from the web. To complete this, you need some tool that will convert MPEG-compressed video files to individual images. If you do this project, tell me where you find the necessary tools in your 9/17 project plan.
in all cases, the most important part of the final project report is a discussion of the results. Given your time constraints, you should not expect success with the more open-ended projects. However, do not be afraid to take risks: a good discussion of a failed attempt makes for a great project report.
While the work presented in your project need not be original, the writing must be yours. Please look at the following documents if you have doubts as to what constitutes plagiarism:
The following is a very useful Duke resource on writing:
|
