(pending further update)
The course project will be an individual project. Two or more people can work on related topic and share the same set of references as well as existing software programs. But each project has to be independently conducted and must have different foci.
Such a report must adhere to high standard in terms of ethics. All quotations and references must be clearly marked. Direct verbatim of an existing paragraph without explicit reference will be considered as an act of plagiarism and will be handled according to university rules.
Project types can be (a) survey type, (b) theory/algorithm type or (c) implementation type.
Survey type -- It should be of a quality similar to a book chapter in an edited book. The length will be at least 30 pages in double-spaced type-written pages including figures, tables and references. At least 30 or more references must be quoted and at least 3 papers must be discussed in details. A good way to present survey paper is to provide "cross-paper" comparision: Comparing, say, method, performance, etc. accross several papers of similar nature. Many of the papers presented in this course are good survey papers and their approach should be carefully immitated. Numerical examples and your own simulation results will be considered as bonus. Suitable topics in this category may include:
Theory/algorithm type -- Project focus on a specific theory or algorithm in image and video processing. The goal is on developing (incrementally) improved version of existing algorithms. Simulation is definitely needed to evaluate the performance. Examples include (to be filled)
Implementation type -- This type of project involve actual code development. However, you do not have to reinvent the wheel if a public domain implementation already exist. You must submit source code you developed with maximum amount of comment. All source code, including those taken from public domain must be submitted in a zipped file. The submitted source code should be well-documented so that it can be compiled independently by the instructor without the presence of its author. This will be an important criterion to determine the quality of the code. The report must explain not only the structure of the whole package (include the public domain part) but also discuss efforts to make the code work as well as performance/cost comparision with existing implementation if applicable. Examples include (to be filled)
Proposal: You should submit an one-page proposal to the instructor for approval of the project. You may want to discuss with the instructor about potential project topics.
Report: A type-written, hardcopy project report, as well as an electronic version (including source code, design files developed) are to be submitted at the end of the semester. The report must be include the following sections:
(a) Introduction: Motivation and backgrounds.
(b) Main body of report. Depending on types of project, this part may include method used, approaches taken, problem description, or survey of a specific subject.
(c) Conclusion and discussion: Highlight your achievement in this project and things may be done in the future.
Presentation: At the last week of the semester, project presentation will take place. a power point presentation will be given in class and later posted on-line. The presentation will be 12 minutes with approximately 15 slides.