The course project is your chance to gain hands on HRI research experience. I highly recommend that you complete this project in a group of 2 or 3. If you wish to complete your project individually, please email me to discuss further. This project must be focused on the interaction between physically embodied robots and 1 or more people. This page contains details on the project deliverables, due dates, as well as suggestions for possible projects (at the bottom of the page).
Due Date | Time Due | Project Deliverable |
---|---|---|
Wed, Oct 6 | 9:30am CST | Pitch 1-3 Project Ideas |
Mon, Oct 11 | 9:30am CST | Draft Project Proposal |
Tue-Fri, Oct 12-15 | 9:30am CST | Refine Project Proposal |
Mon, Oct 18 | 9:30am CST | Finalized Project Proposal |
Mon, Nov 1 | 9:30am CST | Progress Report #1 |
Mon, Nov 15 | 9:30am CST | Progress Report #2 |
Wed, Dec 1 & Fri, Dec 3 | Project Presentations to Class | |
Fri, Dec 10 | 5:00pm CST | Project Final Report |
Put your project pitches in this Google doc.
Once you have formed your team, make a Google Drive folder for your project team that you share with the teaching team (sarahsebo@uchicago.edu and vzhao@uchicago.edu)). You'll turn in of all your project deliverables to this Google Drive folder.
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-3, 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 Topics in HRI 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.
The draft proposal should be 1-2 pages in length and describe:
The finalized project proposal, in addition to what is contained in the draft proposal, should detail a detailed timeline with corresponding intermediate deliverables. Before submitting your final project proposal, please set up a meeting with the teaching team in the range of Tue-Fri, Oct 12-15. You'll receive an email from me (Sarah) on how to sign up for a time to meet with the teaching team to discuss your project proposal.
The progress report should contain:
You will present the work that you've done in your course project on either December 1 or December 3. Half of the project teams will present on each date. You should aim for your presentation to take 12 minutes, leaving 3 minutes for Q&A (I will plan to cut you off if you go beyond 12 minutes). All members of your team are expected to participate in the presentation. Your slides should be uploaded to your team's Google Drive folder by the start of class on the day you 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 have the following sections: abstract, introduction, background, methods, results, discussion, conclusion, and contributions. The abstract - conclusion sections should resemble the papers we have read and discussed in this course. The contributions section should detail the contributions of each team member, detailing which portions of the project were completed by each team member. The report should be approximately 6 pages long without references. Please both 1) send the teaching team an email of your final report and 2) upload a copy to your team's Google Drive folder.
The grading for the course project will be as follows:
For further details on project grading, please check out the final project grading rubric.
Here are some different types of projects you could consider:
This project was inspired by the increasing presence of AI agents into our homes and sought to investigate how these AI agents influence children in a home environment. Specifically, these students studied how parents perceived aggressive interactions of children with several portrayals of AI (a robot, an Amazon Echo Dot, and a houseplant) and whether their parenting style should take another variable into account, given the presence of advanced AI in homes. They conducted a 2x3 between-subjects design: condition (aggressive/neutral) x inanimate object (Nao/Alexa/houseplant). Participants recruited on Prolific watched a 20-30 second video clip of an experimenter interacting with one of the objects in an aggressive/neutral condition and then filled out a Qualtrics survey. They hypothesized that parents and guardians of children from ages three to ten would be more concerned about their child(ren) abusing the Nao robot than Alexa and a houseplant and that the differences in the anthropomorphic and agency attributes of the objects would contribute to the concern. Their results showed that the parents are more concerned about their children’s aggressive behavior towards the robot Nao than the houseplant and Alexa, and about Alexa more than the houseplant. They also found that the attributes of the inanimate object: animacy, likeability, warmth, discomfort, safety, perceived intelligence, and competence levels were significant in parental concern ratings.
Note: This study was conducted on Prolific (a crowd-sourcing platform) because the covid-19 pandemic prevented these students from running any in-person human subjects.
Human-robot touch offers a compelling medium for communication; touch can be used both to perform tasks (instrumental touch) and provide comfort (affective touch). Deliberate, physical contact with humans is especially applicable for healthcare robots because touch is frequently employed and often necessary to provide patients with medical aid and emotional support. To understand the factors that influence how people perceive robotic caregivers, these students conducted a 2x2x2x2 crowd-sourced study on Prolific, where each participant viewed a video recording of one of the students being given a medical exam by a robot and then filled out a Qualtrics survey based on the observed video clip. The students examined how the perceived quality of care is affected by the presence of touch (present or absent), type of touch (instrumental or affective), robot appearance (Nao or Stretch), and robot tone (empathetic or serious). Their findings confirmed that instrumental touch is more important to quality of care than affective touch and were able to suggest several guidelines for designing robot personality and appearance to maximize the warmth, competence, and comfort of a patient’s experience.
Note: This study was conducted on Prolific (a crowd-sourcing platform) because the covid-19 pandemic prevented these students from running any in-person human subjects.
If you are interested in using a physical robot as a part of your project, here are the robots available for you to use in my lab:
Once you are ready to start working with one or more of these robots, please reach out to the teaching team for resources and example code for programming them and also to request access from me (Sarah) to the Human-Robot Interaction (HRI) lab. The HRI lab is located in JCL 379 and is the place where you can find all of the robots and will be a place where we recommend that you spend your time programming the robot(s).
If you plan to conduct a human subjects study in your class project, regardless of whether it is in-person or online (e.g., Prolific), 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.
Ideal World Scenario. If you have unlimited time and resources, you determine the number of participants you should recruit for your study by conducting a statistical power analysis. You can find detailed information on how to conduct a power analysis by going to my "Conducting Statistical Analyses of HRI Data" guide that can be found on the For Lab Members page on my HRI lab website. Click the "Access Lab Wiki" button. You will need to enter the password to enter (please ask the teaching staff for this password). Then find the wiki entry titled "Conducting Statistical Analyses of HRI Data" and the section on "How Many Participants Should I Recruit? A Guide to Conducting a Power Analysis to Determine Experiment Sample Sizes."
Real World Scenario. If you are limited by time and/or resources, then you may be limited to recruit the maximum number of participants you can with the time and money available to you. There is no shame in this, especially given the short time frame of UChicago's academic quarters. If you have any questions about how many participants we, the teaching team, deem as acceptable for you to achieve a good grade on the project, please chat with us about it.
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, either 1) you need a pro account or 2) you can ask me (Sarah) to start a Qualtrics survey on my pro account and I can share it with you. I am more than happy to help you out with option #2, please email me.
These are the most commonly used and recommended pre-existing questionnaires that you might consider using for your human subjects experiment:
If you are interested in running an online or crowd-sourced human subjects study, I would recommend using Prolific. The easiest way to set this up is to create a Qualtrics questionnaire and link to that questionnaire on Prolific.
Timing. Before you launch your study, you will want to have a friend or two take your survey to get a sense of approximately how much time it will take participants to complete your survey. This will also determine how much you will pay each of your participants.
Prescreening Participants. I typically use the following criteria:
Payment. We will pay our participants at the rate of $8.00 per hour. When you are ready to launch your study, you will email me (Sarah) with your Prolific login credentials (please ensure that your password is something you do not mind sharing with me), and I will go into your account and add the appropriate amount of money to your account. Then you can launch your study.
Piloting. It is very important to pilot your study before going ahead and running it. We recommend that you have one or two friends go through your study to ensure that everything makes sense and to catch any typos. Then, ask one of the teaching team members to go through your study, we would love to give you feedback on it. Piloting is essential to work out any kinks and ensure that your study is set up to adequately answer your research questions.
Staging Study Launch. We HIGHLY RECOMMEND that you start out by running 20 or so participants in your study first, so that you can ensure that your study is working properly, before running the rest of your planned participants. To ensure that your study is working, please go through the data you collected in Qualtrics to ensure that participants make it through your survey as you intend and answer the questions as you intend them to.
If you want to run an in-person human subjects study, here's an example timeline of what your project work might look like:
Recruitment. 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.
Payment. For in-person human participants, we will pay them at the rate of $12.00 per hour. We will pay them in the form of Amazon gift cards. To facilitate this payment, please email me (Sarah) 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 gift card for participating in your study.
Piloting 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:
I (Sarah) have created a guide for conducting statistical analysis on human subjects data, complete with a thorough answer to the question "what statistical test should I run?" and examples in R of how to run each statistical test. You can find this guide by navigating to the For Lab Members page on my HRI lab website. Click the "Access Lab Wiki" button. You will need to enter the password to enter (please ask the teaching staff for this password). Then find the wiki entry titled "Conducting Statistical Analyses of HRI Data", which will contain everything you need. If you have any questions about conducting your data analysis, please do not hesitate to reach out to the teaching team.