From BELIV 2010

Presentation

Notes

- look at eye tracking in the entire view, more complicated vis analysis tools

- break vis into views, track what's going on when using views

- integrate eye tracking into improvise

q and a:

- example of use? track pattern of gazes between the filtering control and the filtered results, to see how the filtering is done, see how control is observed (multiple control may have changed)

- anticipate user action and prepare system for it

- don't need eye tracking, but can use mouse tracking? the two together will tell you a lot more, but don't know how the two combine yet, but mouse/eye may be separate

- eye tracking data to be nosier than mouse data, eye tend to lead mouse movement

- multiple level of processing? base scanning of the vis, action

- high level stuff? too complicated? try to tune design and spacing? more space between views