Course project

Timeline

Course projects should be done individually. Two options:

Proposal (5%): one-pager (one line or a short paragraph)
- Specify 1) the chosen topic, 2) programming language, and 3) tools or libraries you will use.
- Example topics: [link]
Final report, code & demo (95%)

Proposal (5%): one-pager (one line or a short paragraph)
- Specify 1) the chosen topic and 2) the list of papers to read.
- Example topics: [link]
Final report & presentation (95%): No less than 10 pages (format: 12-point font size on single-spaced 8.5" x 11" pages).
- Example technical review: [pdf]
- See suggested format (not mandatory) below.

The report should cover 1) how it is an open research problem

A technical review is intended to systematize the knowledge on a focused topic. The following is the suggested structure:

Section 1 Paper Summaries
- Subsection 1.1: Summary of Paper P1
  - Problem studied in P1
  - Approach in P1
  - Evaluation result in P1
  - Technical novelty in P1:
    - How is the problem an open problem that prior research does not cover,
    - or What technical challenges are presented in solving the problem? and How does the paper overcome the challenges?
    - or How does the approach in the paper achieves a better or worse result compared to prior papers? In what metric and what quantity?
  - Strength and limitation of P1
- Subsection 1.2: Summary of Paper P2
  - ...
- Subsection 1.n: Summary of Paper Pn
Section 2 Comparison Framework
- Defining m applicable properties F1, F2, F3, ...
- The table for comparison (example below)
- Open problems and your prediction of future work.