CS 4364 Final Project

  • Final Project is due by Friday, 05/08 at 11:59 PM (EST)

  • Class participation, Google Folder.

  • (Back to Course Index Page)

    • 1. Final Project Overview

    This is a team submission. Each team will submit one final project package.

    Your final project should be written in AAAI format. The paper should follow the AAAI two-column style and should be organized like a short conference paper, with clear sections such as introduction, related work, method, experiments, results, discussion, and conclusion.

    For this course project, your final paper should be up to 7 content pages, plus additional pages for references if needed.

    You should also include a GitHub repository link and a README so that your project is understandable and reasonably reproducible.

    2. AAAI Format Requirement

    • Your final paper must use the AAAI format.

    • Please use the AAAI author kit / template style for the final paper.

    • The paper should be written in a professional academic style, similar to a conference submission.

    • For this course project, target 7 pages of main content. References may continue beyond the main content pages if needed.

    • You do not need to submit supplementary material, but your GitHub repository and README should support the paper.

    3. What to Include in the Paper

    Your paper should clearly describe the following:

    • Problem and motivation: What problem are you solving, and why is it interesting or important?

    • Related work: How does your project connect to prior methods, datasets, or papers?

    • Method: What model, pipeline, or system did your team build?

    • Experimental setup: What dataset, preprocessing, baseline methods, and evaluation metrics did you use?

    • Results: What did your team find? Use tables or figures when helpful.

    • Discussion: What worked well, what did not work well, and what limitations remain?

    • Conclusion: Briefly summarize your final takeaways.

    Your paper should be complete and self-contained. It should explain your project clearly enough that another student can understand the motivation, method, and results without needing additional notes.

    4. GitHub and README Requirement

    Instead of uploading a large code zip file, each team should submit a GitHub repository link.

    Your repository should include a clear README with at least the following:

    • Project title

    • Team member names

    • Short project description

    • Instructions for setup and running the code

    • Description of major files and folders

    • Any important dependency or environment information

    • A short note on how the repository relates to the paper experiments

    Your repository does not need to be perfect, but it should be organized and understandable. The goal is to show clear technical progress and reasonable reproducibility.

    5. Use Lab 10 Peer Review Feedback

    Your team is expected to consider the peer review feedback from Lab 10 when preparing the final project submission.

    Please include a short section in your submission called Response to Lab 10 Feedback.

    In this section, provide a short bullet list describing:

    • one or more major suggestions you received, and

    • what your team revised, improved, clarified, or chose not to change.

    This does not need to be long. A short and honest response is enough.

    6. Submission Guide

    • This is a team submission. Each team only submits one final project package.

    • Submit one ZIP file named final_project_teamname.zip.

    • Your ZIP file should include:

      1. The final paper in PDF format using AAAI style, for example final_paper.pdf

      2. A short response document, for example response_to_lab10_feedback.pdf or .txt

      3. A short text file containing the GitHub repository link, for example github_link.txt

    7. Grading Focus

    The final project will be evaluated using a balanced standard that considers:

    • Paper quality and organization

    • Technical implementation

    • Experimental design and results

    • Clarity and professionalism of presentation

    • Evidence of progress and thoughtful revision

    • Code organization and README quality

    A strong project does not need to have the best performance in the class, but it should show clear effort, sound reasoning, and a well-documented final result.

    8. Notes

    • Submit the final project ZIP file to Blackboard.

    • Final Project is due by Friday, 05/08/2026 at 11:59 PM (EST).

    • Please plan ahead and give your team enough time to revise both the paper and the repository after receiving Lab 10 peer feedback.