Slides and raw slide materials

• For Harold Hawkins

• by Frank Ritter 4 oct 02

• DRAFT slides, a later revision with a live movie coming in the next week

The old:> p s3(state s3 ^input-link i1 ^ew-link e23 ^color red ^plane-status s23 ^location-x 23.34 ^location-y 48.921 ^altitude 23012 ^wingman w23 ^speed 34.5 ^heading 23.4 ^radar-elevation 3 ^lockon set (A7 ^contact C109 ^id I10 ^info I9 ^relative R17 ^state S18 ^tactical A8 ^time-hack T11)(S14 ^copy-of Z5 ^formation F3 ^mission-role lead ^partner growl2 ^radio *none* ^strategy X62)(C104 ^control-point C127 ^control-point N5 ^control-point N3 ^control-point N1 ^control-point R15 ^control-point H5 ^control-point H4 ^home-base H4 ^home-base-launch H5 ^racetrack R15)(C105 ^control-route N7 ^control-route N6 ^control-route N4 ^control-route N2 ^control-route E89 ^control-route L11 ^exit E89 ^launch L11)(Y41 ^count 2 ^max-range 0. ^name sparrow ^type sparrow)(Y42 ^count 2 ^max-range 0. ^name sidewinder ^type sidewinder)(Y43 ^count 4 ^max-range 0. ^name phoenix ^type phoenix)(Z1 ^agl X2 ^alt-above-highest-feature X3 ^altitude X1 ^call-sign growl1 ^climb-rate X4 ^d-fuel X12 ^d-heading X13 ^d-pitch X14 ^d-roll X15 ^d-speed X16 ^debug-cell 33761 ^debug-id 16 ^debug-x 22089 ^debug-y 84014 ^elapsed-time X39 ^flight-dynamics *old* ^fuel X5 ^heading X6 ^iff X17 ^io-pointer 277904920 ^location X42 ^munitions X99 ^pitch X7 ^radar X23 ^radar-azimuth X34 ^radar-elevation X35 ^radar-height X37 ^radar-mode tws-man ^radar-range-minimum X38 ^radar-width X36 ^radio-a-frequency 3.e+07 ^radio-b-frequency 3.3e+07 ^radio-guard-frequency 3.e+07 ^roll X8 ^side blue ^sidewinder-locked *no* ^speed X9 ^status *normal* ^stopwatch-time X41 ^takeoff *yes* ^vehicle-type f-14d ^world-time X40 ^x X10 ^y X11)

)

Current: task specificFuture: Articulate, general

More Articulate Model Interfaces

Queries (111)

Divergent Purposes (5)

Aspects not yet in Current Model (4)

On-Topic Questions (36)

Usefulness of Existing Knowledge Access Tools (33)

VISTA Explanation Facility (6)

Goal Stack (17)

Milestones (9)Radio Log (1)

Lack of Information (7)

Visual Display of Agent Knowledge

(7)

Proposal for New Tool to Access Agent Knowledge (7)

Negative (2)

Positive (4)

Increased Access to Agent Knowledge (35)

Clarity (4)

Content (5)

Superfluous (5)Clarity (4)

Content (6)

What Users Want(based on 12 expert users)

Need For Why-Type Explanation

(14)

Meta and simulation queries and comments (5)

Queries of agent state (36)

Theory of Soar Usability: What Needs to be Explained

• Specific task analysis from usability study of SAP

• General task analysis based on Soar architecture

• Design for interfaces and structures for– More powerful and more complete general

displays– Running explanation and posterior explanation

“A picture’s worth 1000 words…”(1/2)

• A partial “typical” view of data available to users and operators:

(A7 ^contact C109 ^id I10 ^info I9 ^relative R17 ^state S18 ^tactical A8

^time-hack T11)

(S14 ^copy-of Z5 ^formation F3 ^mission-role lead ^partner growl2

^radio *none* ^strategy X62)

(C104 ^control-point C127 ^control-point N5 ^control-point N3

^control-point N1 ^control-point R15 ^control-point H5

^control-point H4 ^home-base H4 ^home-base-launch H5 ^racetrack R15)

(C105 ^control-route N7 ^control-route N6 ^control-route N4 ^control-route N2

^control-route E89 ^control-route L11 ^exit E89 ^launch L11)

(Y41 ^count 2 ^max-range 0. ^name sparrow ^type sparrow)

(Y42 ^count 2 ^max-range 0. ^name sidewinder ^type sidewinder)

(Y43 ^count 4 ^max-range 0. ^name phoenix ^type phoenix)

(Z1 ^agl X2 ^alt-above-highest-feature X3 ^altitude X1 ^call-sign growl1

^climb-rate X4 ^d-fuel X12 ^d-heading X13 ^d-pitch X14 ^d-roll X15

^d-speed X16 ^debug-cell 33761 ^debug-id 16 ^debug-x 22089

^debug-y 84014 ^elapsed-time X39 ^flight-dynamics *old* ^fuel X5

^heading X6 ^iff X17 ^io-pointer 277904920 ^location X42 ^munitions X99

^pitch X7 ^radar X23 ^radar-azimuth X34 ^radar-elevation X35

^radar-height X37 ^radar-mode tws-man ^radar-range-minimum X38

^radar-width X36 ^radio-a-frequency 3.e+07 ^radio-b-frequency 3.3e+07

^radio-guard-frequency 3.e+07 ^roll X8 ^side blue

^sidewinder-locked *no* ^speed X9 ^status *normal* ^stopwatch-time X41

^takeoff *yes* ^vehicle-type f-14d ^world-time X40 ^x X10 ^y X11)

growl1> ps : ==>S: S1 : O: O106 (execute-mission) : ==>S: S27 (operator no-change) : O: O116 (barcap) : ==>S: S28 (operator no-change) : O: O158 (fly-control-route) : ==>S: S36 (operator no-change) : O: O179 (fly-route) : ==>S: S38 (operator no-change) : O: O183 (execute-turn) : ==>S: S39 (operator no-change) : O: O185 (wait)

“A picture’s worth 1000 words…”(2/2)

• SAP view ofthe same data(plus more)

Which would you rather see from a cognitive model?

p s3(state s3 ^input-link i1 ^ew-link e23 ^color red ^plane-status s23 ^location-x 23.34 ^location-y 48.921 ^altitude 23012 ^wingman w23 ^speed 34.5 ^heading 23.4 ^radar-elevation 3 ^lockon set ....)

The Developmental Soar Interface(Ritter & Larkin, 1994)

Other things we’re doing for this project

• Tech report in preparation summarizing transcripts of 12 experts using and commenting on the SAP interface

• Paper submitted to Human-Computer Interaction (journal) on multi-expert usability studies

• CGF conference paper placed on their ‘recommended reading list’ • Review of Jack vs. Soar headed to Hawkins (sent to Ritter for comments by

UK MoD’s Def. Science&Tech Lab). It argues that usability is important and pivotal in choosing an architecture

• Soar workshop report published in AI Magazine (Fall 2002)• Continue to maintain Soar FAQ• Dissemination of ACT-R workshop proceedings to Soar community and vice-

versa