The course project is your chance to gain hands on HRI research experience. You are expected to complete this project in a group of 2 to 4. This project must involve conducting a human-subjects study that answers a novel research question focused on the interaction between a physically embodied robot and 1 or more people. This page contains details on the project deliverables, due dates, as well as examples of prior projects (at the bottom of the page).
| Due Date | Time Due | Project Deliverable |
|---|---|---|
| Wed, Apr 1 | 1:30pm | Pitch 1-3 Project Ideas |
| Tue, Apr 7 | 11:59pm | Draft Project Proposal |
| Wed-Tue, Apr 8-14 | Refine Project Proposal | |
| Tue, Apr 14 | 11:59pm | Finalized Project Proposal |
| Tue, Apr 28 | 11:59pm | Project Deliverables & Update #1 |
| Tue, May 5 | 11:59pm | Project Theoretical Contribution (CMSC 30630 ONLY) |
| Tue, May 12 | 11:59pm | Project Deliverables & Update #2 |
| Mon, May 18 & Fri, May 22 | 12:30pm - 2:30pm | Project Presentations to Class |
| Thu, May 28 | 11:59pm CST | Project Final Report, Teaming Survey, and Data Sharing |
Put your project pitches in this Google doc. All other project deliverables will be submitted on Canvas.
Before pitching project ideas, read this entire web page thoroughly to get the full picture of what this project will entail.
Although the project will be completed in teams of 2-4, these pitches are made by individuals. The purpose of these project pitches is to aid in the formation of project teams (your project proposal can and will deviate from these project pitches, again, the project pitches are meant to serve as a starting point for team formation). In this Google document you'll pitch 1-3 project ideas that you'd be interested in pursuing for the course project. It does not need to be fully formed, but enough to give your classmates a good idea of what the project will entail.
Your draft project proposal should introduce your motivation for your project, the research questions it tries to answer, proposed methods, and an evaluation plan. We encourage you to usethe Lab 1 HRI Study Design Worksheet as a resource and template for the draft project proposal. Your draft proposal should include:
The finalized project proposal, in addition to what is contained in the draft proposal, should include:
Project Deliverables: For this first project deliverable, you will write a first draft of your final paper's introduction and background sections (see detailed instructions on expectations for these sections below in the Final Report section). You are expected to use the the ACM conference template for this submission. You are also expected to include a section on your genAI use for this deliverable, in which you will describe whether you used genAI tools and if so, which tool(s) you used and how you used them.
Project Update: You will also submit a brief update on your project progress that includes:
Students enrolled in the graduate section of the course (30630) will write a 1-2 page theoretical contribution positioning of their course project. If multiple students enrolled in the graduate section are on the same project team, each will need to write and submit their own theoretical contribution.
The purpose of this theoretical contribution positioning is to deepen the conceptual grounding of your project. This assignment is not a summary of prior work. Instead, it should clearly articulate how your project is positioned within, extends, or challenges existing theory in Human-Robot Interaction and related fields. You should:
Project Deliverables: For this project deliverable, you will write a first draft of your final paper's methods section (see detailed instructions on expectations for these sections below in the Final Report section). We realize that you will not be able (yet) to include all the details required for the final paper (e.g., IRB number, preregistraion link, robot code repo link), however, we encourage you to include as many elements as you can at this deliverable deadline, and at minimum:
Project Update: You will also submit a brief update on your project progress that includes:
You will present the work that you've done in your course project during finals period. You should aim for your presentation to take 10-12 minutes, leaving 3-5 minutes for Q&A and transitioning to the next group (I will plan to cut you off if your presentation goes beyond 12 minutes). All members of your team are expected to participate in the presentation. Your slides should be uploaded to Canvas by the start of the class meeting where you will present. Your presentation should highlight the following:
The project report should be written in the style of an academic conference paper (like the papers we've been reading for our class discussions), feel free to use the ACM templates for conferences. The report should be approximately 6-8 pages excluding references and contain the following sections:
Due at the same time as your final report, ensure that you've filled out the course project teaming survey. Assuming that all team members make approximately equal contributions on the course project, all team members will receive the same grade. However, if certain team member(s) do not contribute a sufficient amount of work to the course project, each team member may receive a different grade that reflects their individual contributions.
If you have not done so already, please share all of the data you've collected in your HRI project in a UChicago Box folder and add the teaching team to the shared folder. This includes questionnaire data, video data, and any other data you collected in your project.
The grading for the course project will be as follows:
For further details on project grading, please check out the final project grading rubric.
For running an in-person human subjects study, here's an example timeline of what your project work might look like:
Since you will be conducting a human subjects study in your class project, you will need to submit an IRB (Internal Review Board) Application and have completed Human Subjects Protection Training (← that link contains all the info you need to complete the training). Before you submit your IRB application, you must have already completed the human subjects protection training.
In order to conduct human subjects research in affiliation with UChicago, you must submit and get approved an Internal Review Board (IRB) application. This means that BEFORE you run any human subjects, you MUST have your IRB application approved. For HRI related research, we submit our IRB applications to UChicago's Social and Behavioral Sciences Institutional Review Board (SBS IRB). Their main website, https://sbsirb.uchicago.edu/, contains helpful information, templates, and guidance for completing an IRB application.
The purpose of the IRB is to ensure that UChicago research is being conducted ethically and with proper respect to human participants. Your IRB application will include:
To create, edit, submit, and amend your IRB application go to https://aura.uchicago.edu/ and click on the "IRB" button.
It is most helpful to model your IRB application after one that has already been approved. Please ask the teaching staff to provide you with model IRB application examples to help you as you create your own.
When you complete your own IRB, please put me (Sarah) as the PI and all other teaching team members as collaborators on the personnel list. Since I (Sarah) will be the PI for the IRB, this means that I must be the one to hit the "submit" button whenever you submit the IRB application or revisions to your IRB application. Please email me when you are ready to make an IRB submission, and I will hit that "submit" button.
HRI researchers at the Naval Research Lab and George Mason University have compiled a database of scales HRI researchers use in their studies. I highly encourage you to visit their website Finding the "Perfect" Scale (especially their database page) where you can find questionnaire scales you can use for your study as well as a rating of the quality of each scale.
If your study involves asking human participants to fill out a questionnaire, I recommended that you use Qualtrics. In order to get all the nice bells and whistles that comes with Qualtrics, we highly recommend that you request a pro account. You can do this by completing this User Agreement Form (for more context, see this UChicago ITS post about using Qualtrics at UChicago).
You will be responsible for recruiting your own participants. You can post on social media, send emails, post on UChicago organization sites, etc. Just be sure that you include all forms of recruitment in your IRB application that you plan to use. We recommend you try to recruit the following minimum number of participants, dependent on your group size:
For this class, you will use a Misty II robot for your project. Misty can locomote (using treads), move its arms and head, show different expressions on its face, and talk-back-and-forth with people. We will have 3 labs devoted to gaining experience programming Misty with the Misty Python API.
For in-person human participants, we will pay them at the rate of $12.00 per hour in the form of Amazon or Tango gift cards. To facilitate this payment, please email the teaching team daily when you are running your study with a list of email addresses that correspond with your study participants from that day. I will ensure that they are sent their Amazon or Tango gift card for participating in your study.
It is SO important before you start running real human subjects that you practice, practice, practice executing your human subjects study. We recommend:
Robots that serve as information oracles in collaborative settings must convey expertise while socially engaging those who use them. This team conducted a between-subjects experiment in which pairs of unacquainted university students solved a 15-minute wilderness-survival ranking puzzle while querying a Misty II social robot for information. The robot adopted either a competent or humorous communication style yet delivered the same information in both conditions. The team tested five pre-registered hypotheses: (H1) a competent robot will yield higher team performance but lower perceived human-human bonding; (H2) a humorous robot will strengthen human-human bonding even if task performance dips; (H3) participant personality traits, primarily extraversion, will covary with responses to the robot; (H4) teams in the competent style will outperform those in the humorous style on objective task metrics; and (H5) competent-style robots will be judged more competent, less warm and more discomforting on the RoSAS. Results indicated that participants who worked with the competent robot performed better on the task, while the humorous robot had no noticeable effects on human-human bonding. This study makes the case for prioritizing robot efficiency in teamwork tasks, as interpersonal effects remain constant despite the robot's personality.
Life is a game and there's nothing more that people love than winning. However, losses are inevitable, especially in competitive settings. The team that conducted this study investigated whether robot anthropomorphism can mitigate negative emotions that arise from repeated losses in competitive game settings. This study aimed to better understand Human-Robot Interaction (HRI) in game settings. To address this, participants engaged in three rounds of Connect-4 with a Misty II robot in one of the following conditions: Factory form with LLM generated "robotic voice" (robot) or dressed in a hat and shirt with LLM generated "human voice" (humanoid). The team measured emotional response to losing and engagement through surveys that were completed between rounds and after the three rounds along with a short interview. While there were no statistically significant results regarding emotional response and engagement, it appeared that participants had a more positive experience when interacting with the humanoid condition. These findings highlight how the importance of anthropomorphism varies situationally and raises further questions about robot expressivity and whether anthropomorphism has greater impact in higher-stakes competitive settings.
Robots are becoming increasingly prominent in the entertainment sphere, where they interact with guests in themed environments to tell stories, often in place of human characters. To evaluate the potential benefits of robots in these contexts compared to humans, this team created an interactive puzzle game where either a robot or a human actor serves as a diegetic “game guide” character that is both a cooperative partner and an omniscient game master. In the game, participants solve a crime mystery by asking the game guide for information to complete tasks and for hints to solve puzzles. They conducted a between-subjects study (n = 25) to investigate how players’ game experiences differed when the game guide was a human compared to an embodied robot. Their results showed that participants playing with a robot had more fun, felt more comfortable and less awkward, and made more progress in solving the tasks compared to those playing with a human. These results suggest that robots can be effective alternatives to human actors in broader immersive entertainment contexts such as escape rooms to provide greater enjoyment and promote more social interaction with in-game characters.
The students who worked on this project continued working on this project after the quarter ended and published a paper on this project at the 2022 RO-MAN conference.
This project explored how the addition of eyes to a non-humanoid robot affects human responses to requests for assistance from the robot. The experiment was executed in a public setting (near Peaches on the first floor of JCL), with the Stretch robot asking passers-by for help picking up an item of garbage. Participants interacted with a robot with and without eyes by assisting it to pick up a piece of trash that it audibly requested help with. Most people from whom the robot requested help paused to assess the situation, however, the team found far more participants in the eye condition actually intervening. The no eyes condition had similar rates of participants pausing to view the robot, but these participants more often described confusion about the source of the voice or the intentions of the robot. The team also recorded whether the people that approached the robots were individuals or small groups. They found that all the small groups that they recorded chose to intervene, they believe, because members of small groups were more likely to stop and discuss the robot, as well as to reassure each other about how to assist it.
You can find a fun YouTube video demonstrating this project at this link.