Improving Human-Robot Interaction Jill Drury, The MITRE Corporation Improving Human-Robot Interaction Jill Drury, The MITRE Corporation Collaborators:

Slides:



Advertisements
Similar presentations
HRI A1 (Sukhatme) Monica Nicolescu, Benjamin Kuipers, Cynthia Breazeal, Jennifer Burke, Jana Kosecka, Vladimir Kulyukin, Brian Scassellati, Shri Narayanan,
Advertisements

ATRV-Jr. Interface Human-Robot Interaction: A Straw Man approach to Interface Iteration This presentation will probably involve audience discussion, which.
Game-Based Design of Human-Robot Interfaces Notes on USR design papers ( ) Presented by Misha Kostandov.
User Interface Design Yonsei University 2 nd Semester, 2013 Sanghyun Park.
Observing users Chapter 12. Observation ● Why? Get information on.. – Context, technology, interaction ● Where? – Controlled environments – In the field.
Bastien DURAND Karen GODARY-DEJEAN – Lionel LAPIERRE Robin PASSAMA – Didier CRESTANI 27 Janvier 2011 ConecsSdf Architecture de contrôle adaptative : une.
The Experience Factory May 2004 Leonardo Vaccaro.
Cognitive Colonization The Robotics Institute Carnegie Mellon University Bernardine Dias, Bruce Digney, Martial Hebert, Bart Nabbe, Tony Stentz, Scott.
Software Testing and Quality Assurance
Brent Dingle Marco A. Morales Texas A&M University, Spring 2002
1 / 31 CS 425/625 Software Engineering User Interface Design Based on Chapter 15 of the textbook [SE-6] Ian Sommerville, Software Engineering, 6 th Ed.,
ISAT Working Group Augmented Cognition Eric Horvitz (Chair), Lee Kollmorgen, Randy Pausch, Paul Rosenbloom, Dylan Schmorrow, Jean Scholtz, Allen Sears,
Heuristic Evaluation Evaluating with experts. Discount Evaluation Techniques  Basis: Observing users can be time- consuming and expensive Try to predict.
1 Keeping Track: Coordinating Multiple Representations in Programming Pablo Romero, Benedict du Boulay & Rudi Lutz IDEAs Lab, Human Centred Technology.
Mixed Reality Benefits For Design Perception Phillip S. Dunston, Ph.D. and Xiangyu Wang Construction Engineering and Management School of Civil Engineering.
Multirobot Coordination in USAR Katia Sycara The Robotics Institute
Autonomy Mode Suggestions for Improving Human-Robot Interaction Michael Baker Holly A. Yanco University of Massachusetts Lowell.
IS-0700.A: National Incident Management System, An Introduction
Usability and Evaluation Dov Te’eni. Figure ‎ 7-2: Attitudes, use, performance and satisfaction AttitudesUsePerformance Satisfaction Perceived usability.
Improved Interfaces for Human-Robot Interaction in Urban Search and Rescue Michael Baker Robert Casey Brenden Keyes Holly A. Yanco University of Massachusetts.
Intelligent Agents: an Overview. 2 Definitions Rational behavior: to achieve a goal minimizing the cost and maximizing the satisfaction. Rational agent:
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
User Interface Evaluation CIS 376 Bruce R. Maxim UM-Dearborn.
Review an existing website Usability in Design. to begin with.. Meeting Organization’s objectives and your Usability goals Meeting User’s Needs Complying.
GMD German National Research Center for Information Technology Innovation through Research Jörg M. Haake Applying Collaborative Open Hypermedia.
1 ISE 412 Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Part of a Broader Strategy
Chapter 9 Database Planning, Design, and Administration Sungchul Hong.
CSC271 Database Systems Lecture # 30.
PROJECT RISK MANAGEMENT Presentation by: Jennifer Freeman & Carlee Rosenblatt
These slides are designed to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright.
1 Human-Computer Interaction  Design process  Task and User Characteristics  Guidelines  Evaluation.
Collaborative Work Package Criteria Suitable for accomplishing in a period of 90 days to 1 year. Work should fall within the expertise of one or more consortium.
At A Glance VOLT is a freeware, platform independent tool set that coordinates cross-mission observation planning and scheduling among one or more space.
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Creational Patterns CSE301 University of Sunderland Harry R Erwin, PhD.
Synthetic Cognitive Agent Situational Awareness Components Sanford T. Freedman and Julie A. Adams Department of Electrical Engineering and Computer Science.
J. Alan Atherton Michael Goodrich Brigham Young University Department of Computer Science April 9, 2009 Funded in part by Idaho National Laboratory And.
Introduction to Management
Lecture 7: Requirements Engineering
Frontiers in Massive Data Analysis Chapter 3.  Difficult to include data from multiple sources  Each organization develops a unique way of representing.
INF5200/TOOL5100: CSCW/L Issues in CSCW and groupware Lecture 1, Issues in CSCW and Groupware: Anders Mørch and Sisse Finken INF5200/TOOL 5100,
SmartNets Results Overview SmartNets SmartNets Methods.
Thrust III HRI Studies for Human Factors and Performance Evaluation J. A. Adams (Lead – Task A) P. Hinds (Lead – Task B) C. Breazeal J. How N. Roy MURI.
Chapter 8 Object Design Reuse and Patterns. Object Design Object design is the process of adding details to the requirements analysis and making implementation.
TOOL5100: CSCL Issues in CSCW and groupware A. Mørch, Issues in CSCW and Groupware: Anders Mørch TOOL 5100,
Human Computer Interaction
Design and Implementation of a Rationale-Based Analysis Tool (RAT) Diploma thesis from Timo Wolf Design and Realization of a Tool for Linking Source Code.
Lesson 7 – Microsoft Excel 2010 Working with Tables, PivotTables, and PivotCharts.
Chapter 10. The Explorer System in Cognitive Systems, Christensen et al. Course: Robots Learning from Humans On, Kyoung-Woon Biointelligence Laboratory.
Advanced Decision Architectures Collaborative Technology Alliance Five Lessons Learned in Human-Robot Interaction Patricia McDermott Alion Science and.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Boeing-MIT Collaborative Time- Sensitive Targeting Project July 28, 2006 Stacey Scott, M. L. Cummings (PI) Humans and Automation Laboratory
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
Thrust IIB: Dynamic Task Allocation in Remote Multi-robot HRI Jon How (lead) Nick Roy MURI 8 Kickoff Meeting 2007.
MGT-555 PERFORMANCE AND CAREER MANAGEMENT LECTURE NO
Foundations of Information Systems in Business
Groupware What are the goals of a groupware system? - Facilitation - Coordination - Cooperation - Augmented, supported production Is efficiency the goal?
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
2013 Section Meeting Coaching Workshop Maximizing Coaching Moments with Young Players.
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
A Multi-Touch Display for Robotic Team Control
Chapter 11: Usability © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License.
Software Requirements analysis & specifications
Management of Multiple Dynamic Human Supervisory Control Tasks
Changing the Game The Logic Model
Presentation transcript:

Improving Human-Robot Interaction Jill Drury, The MITRE Corporation Improving Human-Robot Interaction Jill Drury, The MITRE Corporation Collaborators: Holly Yanco, UMass Lowell Jean Scholtz, NIST Mike Baker, Bob Casey, Dan Hestand, Brenden Keyes, Phil Thoren (UML)

Methodology for Evaluating HRI Two approaches: field and laboratory Field work: so far, robotics competitions See many different user interfaces but have no control over what operator does See many different user interfaces but have no control over what operator does Difficult to collect data Difficult to collect data Can see what they did – but there isn’t time to determine why Can see what they did – but there isn’t time to determine why Best used to get an idea of the difficulties in the real world Best used to get an idea of the difficulties in the real world Can identify “critical events” but don’t know for certain whether operator was aware of them Can identify “critical events” but don’t know for certain whether operator was aware of them

Methodology for Evaluating HRI Laboratory studies Take what we learned in the real world and isolate factors to determine effects Take what we learned in the real world and isolate factors to determine effects Repeatability is still difficult to achieve due to fragile nature of robots Repeatability is still difficult to achieve due to fragile nature of robots

Analysis Frameworks Taxonomy to define human/robot system Detailed definition of human-robot interaction awareness Coding scheme/metrics for analyzing data Scholtz’ evaluation guidelines

Taxonomy Autonomy Amount of intervention Human-robot ratio Level of shared interaction Composition of robot teams Available sensors Sensor Fusion CriticalityTimeSpace

Awareness as a concept from CSCW CSCW software: “...makes the user aware that he is part of a group, while most other software seeks to hide and protect users from each other” [Lynch et al. 1990] “...makes the user aware that he is part of a group, while most other software seeks to hide and protect users from each other” [Lynch et al. 1990] HRI software: Makes humans aware of robots’ status and activities via the interface Makes humans aware of robots’ status and activities via the interface

What is “awareness”? No standard definition in the CSCW field We’ve seen at least 16 different definitions! We’ve seen at least 16 different definitions! Are many different types of awareness, e.g. Concept awareness Concept awareness Conversational awareness Conversational awareness Group-structural awareness Group-structural awareness Informal awareness Informal awareness Peripheral awareness Peripheral awareness Common thread: understanding that participants have of each other in a shared environment Situation awareness Situation awareness Social awareness Social awareness Task awareness Task awareness Workspace awareness Workspace awareness

But CSCW systems are different from robotic systems… CSCW: Multiple humans interacting via a CSCW system Multiple humans interacting via a CSCW systemRobotics: Single or multiple humans interacting with a single or multiple robots Single or multiple humans interacting with a single or multiple robots Non-symmetrical relationships between humans and robots; e.g., differences in Non-symmetrical relationships between humans and robots; e.g., differences in Free will Cognition

Tailoring an awareness definition for HRI: a base case Given one human and one robot HRI awareness is the understanding that the human has of the location, location, activities, activities, status, and status, and surroundings of the robot; and surroundings of the robot; and the knowledge that the robot has of the human’s commands necessary to direct its activities and the human’s commands necessary to direct its activities and the constraints under which it must operate the constraints under which it must operate

An awareness framework: General case Given n humans and m robots working together on a synchronous task, HRI awareness consists of five components: Human-robot awareness Human-robot awareness Human-human awareness Human-human awareness Robot-human awareness Robot-human awareness Robot-robot awareness Robot-robot awareness Humans’ overall mission awareness Humans’ overall mission awareness

General case: a detailed look Given n humans and m robots working together on a synchronous task, HRI awareness consists of five components: Human-robot: the understanding that the humans have of the locations, identities, activities, status and surroundings of the robots. Further, the understanding of the certainty with which humans know this information. Human-robot: the understanding that the humans have of the locations, identities, activities, status and surroundings of the robots. Further, the understanding of the certainty with which humans know this information. Human-human: the understanding that the humans have of the locations, identities and activities of their fellow human collaborators Human-human: the understanding that the humans have of the locations, identities and activities of their fellow human collaborators

General case, concluded Robot-human: the robots’ knowledge of the humans’ commands needed to direct activities and any human-delineated constraints that may require command noncompliance or a modified course of action Robot-human: the robots’ knowledge of the humans’ commands needed to direct activities and any human-delineated constraints that may require command noncompliance or a modified course of action Robot-robot: the knowledge that the robots have of the commands given to them, if any, by other robots, the tactical plans of the other robots, and the robot-to- robot coordination necessary to dynamically reallocate tasks among robots if necessary. Robot-robot: the knowledge that the robots have of the commands given to them, if any, by other robots, the tactical plans of the other robots, and the robot-to- robot coordination necessary to dynamically reallocate tasks among robots if necessary. Humans’ overall mission awareness: the humans’ understanding of the overall goals of the joint human- robot activities and the measurement of the moment- by-moment progress obtained against the goals. Humans’ overall mission awareness: the humans’ understanding of the overall goals of the joint human- robot activities and the measurement of the moment- by-moment progress obtained against the goals.

Coding Scheme: Problems Relating to Critical Incidents Critical incident: Robot has, or could, cause harm or damage Types of problems: Local navigation Local navigation Global navigation Global navigation Obstacle encounter Obstacle encounter Vehicle state Vehicle state Victim identification (specific to search and rescue) Victim identification (specific to search and rescue)

Some Metrics for HRI Time spent navigating, on UI overhead and avoiding obstacles Amount of space covered Number of victims found Critical incidents Positive outcomes Positive outcomes Negative outcomes Negative outcomes Operator interventions Amount of time robot needs help Amount of time robot needs help Time to acquire situation awareness Time to acquire situation awareness Reason for intervention Reason for intervention

Scholtz’ Guidelines (tailored) Is sufficient status and robot location information available so that the operator knows the robot is operating correctly and avoiding obstacles? Is the information coming from the robots presented in a manner that minimizes operator memory load, including the amount of information fusion that needs to be performed in the operators’ heads? Are the means of interaction provided by the interface efficient and effective for the human and the robot (e.g., are shortcuts provided for the human)? Does the interface support the operator directing the actions of more than one robot simultaneously? Will the interface design allow for adding more sensors and more autonomy?

Design Guidelines Enhance awareness Provide a map of where the robot has been Provide a map of where the robot has been Provide more spatial information about the robot in the environment to make the operators more award of their robot’s immediate surroundings Provide more spatial information about the robot in the environment to make the operators more award of their robot’s immediate surroundings Lower cognitive load Provide fused sensor information to avoid making the user fuse data mentally Provide fused sensor information to avoid making the user fuse data mentally Display important information near or fused with the video image Display important information near or fused with the video image

Design Guidelines, concluded Increase efficiency Provide user interfaces that support multiple robots in a single window, if possible Provide user interfaces that support multiple robots in a single window, if possible In general, minimize the use of multiple windows and maximize use of the primary viewing area In general, minimize the use of multiple windows and maximize use of the primary viewing area Provide help in choosing robot modality Give the operator assistance in determining the most appropriate level of robot autonomy at any given time Give the operator assistance in determining the most appropriate level of robot autonomy at any given time

Fusing Information Victims can be missed in video images

Fusing Infrared and Color Video

Other Sensor Modalities for USAR CO 2 detection Audio

Overlay of four sensor modalities