Final Project
Note: This project list is a living document. More information will be added as we move forward. Check Canvas for the latest updates and official deadlines.
Project Proposal
You are required to submit a 2-3 page proposal with at least 3 references (peer-reviewed articles) about the project you want to work on. Submit a PDF that contains the following:
- Group Members: List all members and describe what each person will be doing
- Introduction: 1 paragraph
- Motivation: 1 paragraph explaining why this is important
- State-of-the-Art (Background): Make the case for where we are currently and why you are working on this problem
- Description of the Project: Describe what you are planning to do
- Technology: Describe the technology you will use
- Deliverables: What you will deliver at the end of the semester (be specific)
- Contribution: What would be the contribution of this project
You will submit a PDF in Canvas. You can use LaTeX or a word processing application (e.g., MS Word); however, note that we will use LaTeX for the final paper.
Deadlines
See Canvas for submission and official deadlines. Here are the current deadlines, but remember this site is updated slowly compared to Canvas, which is the main submission system for our class. Dates may be subject to change.
- Finalize Group Stage: 01/29/2025
- Proposal: 02/19/2025
- Checkpoint #1: TBA (See Canvas)
- Checkpoint #2: TBA (See Canvas)
- Final Submission: TBA (See Canvas)
Project Information
In addition to the information provided during the first two weeks and in the syllabus, this page contains more detailed information.
The project will require the use of LaTeX. You will need to upload the PDF and the source for the LaTeX document.
Core Rubric
Here you will find the core rubric. An expanded rubric will be added later to provide additional guidance. Even if you won't run human-subject experiments, I'm requiring you to have the CITI certificate, as this class will touch on human-subject experiments. Without CITI training, you will receive a zero on your final project.
Final Project: 350 points
- Proposal: 5 points
- Checkpoint 1: 15 points
- Checkpoint 2: 20 points
- Project (Programming, experiment, and research paper): 310 points
Project Breakdown (out of 310 points):
- Research Paper (must use template): 70 points
- Experiment Design / System or Experiment Design: 25 points
- Evaluation: 25 points
- Prototype: 150 points
- Presentations: 20 points
- GitHub Repo (or similar): 5 points
- Files (readme files in required places, e.g., Canvas, GitHub, etc.): 5 points
- Videos (other than presentation): 5 points
- Group member evaluation: 5 points (if working solo, the 5 points go to the overall project/paper)
- Overall evaluation: 10 points
Research Paper Breakdown (70 points):
- Overall paper: 25 points
- State-of-the-Art: 20 points
- Methods and Evaluations: 20 points
- Prototype description and reproducibility: 5 points
- Limitations, Future Work, and Conclusion: 5 points
Important Notes:
- Grades are subject to the number of group members. The professor reserves the right to deduct points for other problems not listed here.
- Failure to use LaTeX in the final paper will cost you 25 points. Additional points will be deducted during checkpoints as well.
About LaTeX
I am going to require that you write your research paper (starting with Checkpoint 1) in LaTeX. I have never had anyone lose points (up to now) because of formatting when they used LaTeX. LaTeX can be used via Overleaf (web interface) or by installing it on your computer.
- Mac OS X: I recommend MacTeX
- Windows: I recommend TeXLive
- Linux: It may be installed, or you may need to install it using your package manager
If you use LaTeX on your computer, you can use the built-in editor that the LaTeX distribution may include or use one of your own preference. For example, Visual Studio Code (that runs on Linux, Windows, and Mac OS X) supports LaTeX. I personally use Sublime, but I have tried VS Code as well. VS Code is free; Sublime is not. In reality, you can use any editor: Vim, Emacs, Notepad. Use what you like.
I will provide templates in LaTeX for you to write your final report. See Canvas for LaTeX templates.
About the Final Project
This year, I would like us to concentrate on a few themes: the VR Desktop of the future or the gaming of the future. I will cover them in class. Of course, I'm open to other projects. In CS 464, you saw quantitative experiment design. While this is acceptable if you want to go this route, I will cover qualitative studies, as I think they will serve as a different way of conducting user studies, which is also very useful for early prototyping and industry. I may slightly cover quantitative experiments if time and interest are available.
Regardless of what we do, the project must be related to 3D User Interfaces with an interaction technique focus. The class is multimodal interaction. Therefore, anything that is unimodal and multimodal interaction is acceptable. All projects have to either be based on existing research or focus on improving interaction, while always being grounded in peer-reviewed material.
You are not required to have a novel approach (though it is always encouraged). Evaluating existing approaches, maybe asking different questions, etc., are always welcome. You will need CITI Training. If you want to publish this later, you will need an IRB protocol approved (this may be of interest to people working with other faculty).
GitHub Link
You can find older projects here: https://github.com/NUIG
Group Members
The ideal group size is 3. Groups of 2 can also be formed without my approval. Any groups with one, four, or five members must be approved by me. Smaller groups may not be able to get equipment from me.
Group Size Information
Here you will find further information about the differences of each group size. In addition to the number of people and what I would expect from a group of 3 versus a group of 2, here are other differences:
Group of 1:
- You will be required to have at least 8 peer-reviewed articles in your final report
- Research report should be 4-6 pages + references
Group of 2:
- You will be required to have at least 16 peer-reviewed articles in your final report
- You will need two types of evaluations. One of them must be a controlled study
- Research report should be 6-8 pages + references
Group of 3:
- You will be required to have at least 24 peer-reviewed articles in your final report
- You will need three types of evaluations: one must be a controlled study, one of your choice, and one selected by the professor
- Research report should be 12-14 pages + references
Group of 4:
- You will be required to have at least 32 peer-reviewed articles in your final report
- You will need three types of evaluations: one must be a controlled study, one of your choice, and one selected by the professor
- Research report should be 12-14 pages + references
Important Notes:
- For any group size, the maximum number of pages is 16 (but I don't need long reports). Appendices are welcome only when needed.
- Prototypes will be weighted by the number of group members. I will ask questions about the prototype and other items in the project to assess similar contribution among group members. No free riders.
Checkpoints
In order to avoid leaving the project for the last few weeks, there will be multiple checkpoints.
Each checkpoint will include the following:
- A video (3-5 minutes) discussing the current state and showing what has been accomplished
- A video discussing code (3-5 minutes)
- Push to GitHub all the updated source code (you may push every day if you like) and documents
- GitHub must include a readme file with links to the videos and links to LaTeX files/Word files. Additional documents may be included in this repository
- Additional videos may be uploaded and referenced if needed
- Each checkpoint will have its own requirements
Final Project To-Do List
- Final Report: Using the template provided. Length depends on the number of people you have and the system contribution you have delivered. Additional information will be given in class during a lecture about writing research papers in HCI. Then this will be updated.
- Deliver all files (see next section that talks about structure for upload)
- Deviation from any of the required work will cost points. Not using the template provided or an approved template will cost points. Not delivering a professionally looking document will cost points.
How to Upload Final Project
Upload a zip file. If the zip file is too large, a link to a downloadable file must work. If your link doesn't work for me, you will lose points until I can get the link (and those points will not be recovered). Following instructions is paramount. For example, you must test the link using an anonymous link to make sure it works. Don't assume anything.
Create a zip file with the following structure:
- Create a top directory with the name of your group
- Place the following items inside:
- Final Report PDF
- Readme file with links to videos and the URL of your site
- Directory for "Latex Source" (and include all the LaTeX source there)
- Directory for "PDFs-LiteratureSurvey" with PDFs you found (exclude books, websites, etc.)
- Directory for Source Code (if it fits. If it doesn't fit, create a text file with the link to GitHub)
Videos (What do you need?)
- Short video: No more than 5 minutes, ideally 3. High-level overview of the project. Make it really cool.
- Presentation Video: You pick the length. As long as you can explain your project. No more than 30 minutes. Ideally 12 minutes.
- Programming Video: Explain the code.
You must provide a link in the readme file to view them. You will also need to provide a link to download the actual video files.
Please verify with me if you are not sure. Don't make assumptions.
Programming Language
You can use any language or engine. Most students tend to use Unity Game Engine or Unreal Game Engine. A few have tried Godot.
Instructor and TA's Final Review
You may be required to present your final project to the Instructor and/or the TA. A schedule will be provided either in class or outside of class. Individual members may be asked questions about the code to understand individual contributions.
Grades for Groups
I reserve the right to change an individual's grade if the contribution was not similar to the rest of the peers in the group.
Equipment Available
Your group can request a VR head-mounted display. We will decide if you get a Quest 2 or Quest 3 depending on availability. For online students, we will do our best to provide one to each student.
- Logitech Pen (one per group, limited quantities)
- In certain cases, we have additional devices that we may be able to loan. This includes Leap Motion devices, TILT 5 AR glasses, and a few others.
- In extremely limited quantities, we may be able to loan a laptop for online students. This is not guaranteed.
- Maybe a HoloLens 2
Group Evaluations
Outside of the final project grade, as you can see in the rubric, there will be group evaluations. This is an individual form where you tell us about the progress of your group.
Projects You Can Build From
The NUILAB has projects you can use to build from. We keep this source code private until we are ready to release it. Therefore, anything you do may be used (and you will be acknowledged) for our project in the future. You will also not be able to distribute this software without my authorization. Here is a list:
- Kitchen AR Game: Currently open-source. Works with Microsoft HoloLens 2 for notification interaction research. You may convert this to a Quest platform. (Unity)
- VR Sketching: (Unity)
- Wind Educational Project for VR: (Unreal Game Engine)
- Forest Bathing: (Unreal Game Engine)
- Assembly VR Task: (Unity. Old code, so it may need to be updated)
For more information and the latest updates, please check Canvas regularly.