Code of Honor

This project is intended to deepen your understanding and develop your skills, and it forms a substantial part of your final evaluation. It must be completed collaboratively as a group. Any form of academic dishonesty is a violation of the Code of Honor. You are encouraged to use publicly available resources, provided that all sources are clearly cited and your individual contributions are clearly explained. Failure to properly acknowledge your contribution may be considered a lack of participation, and projects without meaningful individual contributions will be deemed incomplete.

The project topic should be defined, such that it covers at least two topics covered in the course. The groups must conduct background research, contribute to implementation, conduct enough experiments, and use their findings to draw a conclusion. The topic of the project can focus on a hands-on project and/or an interesting research study. Regardless of the topic of the project, the following steps should be addressed:

  1. Make a group of 3. Due to the course size, smaller group size is only accepted under special circumstances.
  2. Do your research and choose your topic by the end of Week 6 (June 20). It is strongly suggested to choose as soon as possible to get into the problem and start preliminaries.
  3. You will be allocated to a TA, who could help you throughout the project.
  4. Present your final result by Week 13 (second Week of August).
  5. Deliver the paper and code by Week 14 (third Week of August).

Submission Procedure

The main body of work is submitted through Git. In addition, each group submits a final paper and gives a presentation. In this respect, please follow these steps.
  • Each group must maintain a Git repository, e.g., GitHub or GitLab, for the project. By the time of final submission, the repository should have:
    • Well-documented codebase
    • Clear README.md with setup and usage instructions
    • A requirements.txt file listing all required packages or an environment.yaml file with a reproducible environment setup
    • Demo script or notebook showing sample input-output
    • If applicable, a /doc folder with extended documentation
  • A final report (maximum 5 pages) must be submitted in a PDF format. The report should be written in the provided formal style, including an abstract, introduction, method, experiments, results, and conclusion.
    Important: Submissions that do not use template are considered incomplete.
  • A 5-minute presentation (maximum 5 slides including the title slide) is given on the internal seminar on Week 13, i.e., Aug 10 to Aug 14, by the group. For presentation, any template can be used.