...
and be on this page in plain text (with some formatting):
20-Feb-2011
Sreeja @ Task Analysis: SPHERES-wise, the goal is to be able to track the state of the robot graphically on a mobile device instead of from a stationary point. It allows for user mobility.
Preconditions - establish comm between robot and mobile device. info known has to be which satellite he is interacting with, which frequency he's on, what data he is viewing, which expt/test he's on.
where is the task performed: on the flat floor or lab table for 3DOF testing and on the ISS for 6DOF microgravity testing
environment on the ISS is very cluttered on the edge of the arena, flat floor is relatively flexible. but we have to always take care to not stand in between the bot and the global metrology system (which is 6 beacons around the floor)
Time required - couple of hours of testing, about once in a month per researcher.
Task is learned by trying it, watching others, reading the manual
| Wiki Markup |
|---|
Sreeja @ Domain Analysis: I like Dimitar's chart and would not change much. Could you be a little clearer on what the numbers mean though? X\[Y-Z\] \-> what does X,Y,Z mean in the context of the relationship? |
19-Feb-2011
Dimitar: I disagree that this is the only class of users: -- both good points, I agree (--Andy)
...
How often is the task performed
daily
Time constraints
1-2 hour sessions
How is the task learned
self-taught
explained by other researcher in lab
What can go wrong
task can be very dangerous for the robot itself
one user was working on a dynamic control task which, if failed and the robot was not stopped, would damage the robot within 1/2 second
that user also relied on a dangerous propeller for propulsion
another user's platform can be damaged by inattention for more than a few seconds when in an unstable state.
failure to connect (wrong info, bad network connection, etc)
Who else is involved
- not sure here... need to think on this more.Sreeja: SPHERES-wise, the goal is to be able to track the state of the robot graphically on a mobile device instead of from a stationary point. It allows for user mobility.
Preconditions - establish comm between robot and mobile device. info known has to be which satellite he is interacting with, which frequency he's on, what data he is viewing, which expt/test he's on.
where is the task performed: on the flat floor or lab table for 3DOF testing and on the ISS for 6DOF microgravity testing
environment on the ISS is very cluttered on the edge of the arena, flat floor is relatively flexible. but we have to always take care to not stand in between the bot and the global metrology system (which is 6 beacons around the floor)
Time required - couple of hours of testing, about once in a month per researcher.
Task is learned by trying it, watching others, reading the manual
Dimitar:
Domain Analysis
Andy:
...