Current Work:
11 June:
Deep in the analysis phase, with a visualization tool to accompany the data crunching...
06 May:
Data collection continues.
16 April:
09 April:
An initial look at two participant's data...
|
Participant A |
Participant B |
Total flight log time (a) |
492 sec |
434 sec |
Total dwell time (b) |
402 sec |
385 sec |
a/b |
81.7% |
88.7% |
Number of fixation points |
1144 |
653 |
Number of OTW-MAP view changes |
263 times |
164 times |
Number of instrument panel gaze points (c) |
2034 |
17 |
Number of total gaze points (d) |
29214 |
25852 |
c/d |
7.0% |
0.066% |
25 March:
Interesting wired article: Eye-Tracking Tablets and the Promise of Text 2.0
"...define words if you stare at them puzzled, eliminating non-essential information when you’re skimming, helping you pick up exactly where you left off..." Read More http://www.wired.com/epicenter/2010/03/eye-tracking-tablets-and-the-promise-of-text-20/#ixzz0jHm2NoDz
Reconfigured display based on calibration runs with several different users. Map display is now at the same level as the user and in the same vertical plane as the out the window display.
During critical phases of the navigation task (i.e. high stress, struggling) users tended to change head position significantly. This makes tracking the map gaze intersection extremely difficult.
16 March:
Added a 'playback' capability using VBA in excel. Displays aircraft track, map and otw intersection points.
From CP 01 to CP 02. Map scan (red squares) is systematic and aligned with intended route and out the window scan (greeen triangles.)
Added instrument cluster: compass, RADALT, BARALT, digital clock.
13 March:
Adjusted saccade threshold from default of 8.2 degrees to 3.2. Also reduced network buffer to reduce 2-3 second delay between facelabs update and out the window eye-scan intersection point visualization update. Need to look at post-process data visualization for correlation. Also look at creating polygons per dwell. Color code or adjust height proportional to time?
12 March - some data points appear to be somewhat random. The middle of the three red data points represents a saccade.
