Image and Video Processing Project Guidelines

Course Project Requirements:

This course requires a project to be performed by two to three students in a group. A project includes the following phases: forming project partner(s), choosing a project topic, writing a project plan, conducting the project, writing a midterm project report, presenting the project in class, and writing a final project report.

Project Content:

A project usually consists of reading papers in the chosen area, comparing performances of different approaches, and perhaps proposing your own algorithms/improvements, and implementing one or two of them.

You are welcome to discuss with me about the possible topics before the project plan is due.

Project Plan (2-4 pages, single column):

The project plan should include the following:

  1. Project title and team members. List your project mentor if you have one.
  2. An abstract: In one paragraph or two, describe briefly the project scope and what you hope to accomplish.
  3. Project schedule: It should include a list of subtasks that you plan to accomplish. For each subtask, describe how you plan to approach it, who in your team is primarily responsible for it, and the deadline for completing it. You should allocate time for literature search, preparing the final report, and final presentation, in addition to the reading/simulation work you plan to do.
  4. List of references: This includes papers and documents and possibly web links that you have found that are relevant to your project topic. Please include complete citation of each item: author, title of the article, journal or book name, and if appropriate, the URL where you get the information. Please follow the IEEE paper reference styles.

A Note About Literature Study:

A good way to search scholarly papers is via Google Scholar. If you identified a paper on the web but cannot find the full paper, you can try to use NYU library databases to obtain PDF copies of the paper. NYU library has online IEEE and ACM databases that include all papers published by IEEE and ACM.

Midterm Project Report (3-5 pages, double column style of IEEE papers):

You can think of the midterm report as a preliminary version of your final project report. It consists of all sections to be included in the final report, except that you will have one section describing the remaining work to be accomplished, in lieu of the Summary Section of the final report.

  • Project title and team members (including the name(s) of your project mentor)
  • An abstract
  • Overview of the project: Describe the subtasks and who is responsible for which subtask if you have multiple members on the team.
  • Project accomplishment: Describe what you have accomplished so far. This can be divided into multiple sections, each section describing one subtask that you have worked on. For each subtask, describe the problem, the method (review of prior approach you plan to implement or your approach), what you have done and learnt. If your project includes a comparison of different systems/techniques, you may have separate sections describing each system/technique and another section comparing these systems/techniques and summarize the pros and cons of each. You may have another section describing your proposed solution. You should have a result subsection that describes the results of various techniques evaluated. Alternatively, you could describe the results of each subtask in each subsection. Literature review could be one subsection.
  • Remaining work: Describe what additional work needs to be accomplished and your plan in accomplishing them, including who is responsible for what and the timeline.
  • List of references: Update from your project plan as appropriate. The reference citation must be complete including all information (authors, title of journals/conferences, year, and URL if it is an online document). Please follow IEEE style.

Final Project Report (4-6 pages, double column style of IEEE papers):

The final report should be a revised version of your midterm report, with updates in each section, except that the “Remaining Work” section will be replaced by the “Summary” section, and a new section on the project depository.

  1. Summary: This section should briefly summarize your findings and what you have learnt. It should also include a discussion of future works that you think should be studied.

  2. Depository of your project outcome: You should save all your work, including source code, executable, data used, results, in a location that can be shared with us (Github, Google Drive, or Dropbox), and you should provide the link to the repository in your report.

Project Content:

Final Project Presentation:

A ~10 minutes oral presentation, with demonstration of computer implementations. Time allocation depends on the number of projects to be presented and the number of team members. You should prepare a presentation file using a computer software (e.g., PowerPoint).

  1. You will be giving the presentation in person or via Zoom.
  2. If you want to include any demonstration in your presentation, please make sure it can be presented directly from your computer.

Suggested Outline for Your Presentation:

  • Project title and team members
  • Overview of your project: The overall goal and subtasks, and who is responsible for what.
  • Describe each subtask: What you did and what you learnt/designed.
  • Demos, if appropriate
  • Summary

If you have more than one person on the project team, please prepare the presentation in such a way that each person on your team can present different parts of it. A two-person team is typically given 10 minutes, a 3-person team 13 minutes, a single-person team 7 minutes. You should practice your presentation in advance to make sure that you know how to share your presentation over Zoom and how the team members coordinate and that you will complete on time.

Note on Plagiarism and Proper Acknowledgement:

Please note that you should not copy sentences/paragraphs or software codes from other documents! You should give full credit to any source (e.g., a graph or a paper) that your work references. Please read the paragraph about plagiarism and proper acknowledgement of references in NYU Student Code of Conduct carefully. All electronic submissions (project plan, report, and presentation) will be checked through Turnitin service on NYU Classes interface, to check for plagiarism. You will get a grade of zero for any work submitted that is found to violate this rule. You are recommended to upload your submission at least several hours before the deadline, so that you can see the result from Turnitin. This way, you will have time to revise if Turnitin reports excessive duplications from public sources.

Please also note that you cannot use the same project for multiple courses, whether a project you have done in the past, or concurrently for multiple classes.

Project Content:

Rubric for Project Grading:

Projects contribute 30% of the total score of the class. The breakdown is as follows:

  • Proj Proposal (2 pt):
    • Good description of project scope (2pt)
    • Detailed project schedule with milestones and who is responsible for what (2pt)
    • Correct listing of references (in proper format) and cross reference from the body (1pt)
  • Proj Midterm Report (3 pt):
    • Organization of the report (does it have all the elements recommended and were the methods and results presented completely and explained well) (2pt)
    • English correctness (1pt)
    • Graphic support for the idea and results (1pt)
    • Correct listing of references (in proper format) and appropriate citation of references (1pt)
  • Proj Final Report (5 pt):
    • Organization of the report (does it have all the elements recommended and were the methods and results presented completely and explained well) (2pt)
    • English correctness (1pt)
    • Graphic support for the idea and results (1pt)
    • Correct listing of references (in proper format) and appropriate citation of references (1pt)
  • Proj Presentation (10 pt):
    • Organization of the presentation (does it have all the elements recommended) (2pt)
    • Clarity in speaking (2pt)
    • Graphic support (2pt)
    • Ease of understanding (as an audience, did you understand what was presented?) (2pt)
    • Time duration (very close to allocated time) (1pt)
    • Was each member of the team appropriately contributing? (1pt)
  • Project Content (10 pt):
    • This will be evaluated based on your project scope as reflected from your presentation and report.
    • 9-10pt for a project without innovation but shows thorough understanding of the reference papers, gives sufficient and clear technical description of the reference papers, and had comprehensive evaluation and testing by comparing several options (in one paper or multiple papers).
    • 7-8pt for a project without innovation and shows good understanding of several reference papers and had complete evaluation and testing of one idea; or projects with scope similar to the first category, but did not give sufficient and clear technical description of the ideas and the results.
    • 5-6pt for a project that is based on one idea in a single paper or your own idea that is very basic (i.e., no citation of relevant prior works and why your approach may be better in some sense), had complete evaluation and testing of the idea.
    • 0-4pt for a project that has incomplete evaluation and testing of one idea.
  • 2 bonus points for a project with some technical innovation: This includes sound ideas that are beyond what is in the reference papers, sufficient and clear technical description of ideas in the reference papers and your novel ideas, and comprehensive evaluation and testing of your ideas by comparing your ideas with some ideas in the reference papers.