Miller Robotic Interface II Bedienungsanleitung PDF herunterladen (Seite 23)

procedure often used a script to be sure that the mission was presented identically to each test

subject. We wanted to simulate the stress of a real search and rescue mission by creating a sense

of urgency. The subject is assured beforehand, however, that the test may be discontinued at

any time without any consequences or ill feelings whatsoever.

3.3 Data Collection and Analysis

During a run, the interface screen was captured directly from the graphics card. In addition,

there was an “over-the-shoulder” camera that recorded the user's interaction with the interface

controls as well as the user's think-aloud comments [Ericsson and Simon, 1980]. Think-aloud is

a study protocol where the test subject verbally expresses their thoughts while performing the

task assigned to them. They are asked to express their thoughts on what they are looking at,

what they are thinking, why they are performing certain actions and what they are currently

feeling. This allows the test administrators to establish the reasoning of why the subject is

performing the task in a specific way. There was usually paper and a pencil at the testing station

for the user to make notes, draw maps, etc. at their discretion. We figured if the subject chose to

use the paper, it could give us ideas about what was missing from the interface. Very often, the

test participants did not make use of the paper.

A cameraman and mapper followed the robot through arenas to create a record of the robot's

progress through the test course. The mapper recorded critical incidents on the map and when

they occurred. The map and video data was used for post-test analysis to determine hits and

also to settle any data collection errors if needed.

The test administrator signaled the start and end of the run to the robot crew via a 2-way radio.

Occasionally, a hardware failure, such as lost communications or dead robot batteries, forced a

restart. This restart was conducted without penalty to the user's run time. Sometimes, an

operator would drive recklessly and cause damage to the environment or the robot. In these

cases, the people following the robot could use their discretion to stop the robot and have the

administrator advise the test subject what happened. The run then resumed from that point.

During the run, the test administrator took notes on the subject's think-aloud comments,

actions, etc. They often recorded if the subject seemed confused or frustrated, but never offered

any kind of help or advice to make them less confused. Sometimes the administrator would ask

1 2 ... 18 19 20 21 22 23 24 25 26 27 28 ... 79 80

Keine Kommentare

Miller Robotic Interface II Bedienungsanleitung Seite 23