Data Files
©
2016-2017 SR Research Ltd.
87
BUTTON
buttons 1-8 state and change flags
STATUS
warning and error flags
INPUT
input port data lines
The default data are:
file_sample_data =
LEFT,RIGHT,GAZE,GAZERES,PUPIL,HREF,AREA,HTARGET,STATUS,INPUT
Usually, data for both eyes are enabled, and the menus in the EyeLink tracker
are used to set which eye is actually tracked. Recording of gaze and pupil area
is essential for most work, and resolution is important if velocity is to be
computed later. Recording of HREF data is optional.
For the EyeLink Remote, the HTARGET flag should always be included in the
recording.
4.6.2 Event Data
Eye-movement events are generated by processing one of the types of eye
movement data (PUPIL, HREF, or GAZE) as specified by the
"recording_parse_type" command (the default setting is GAZE). This command
may be edited in the DEFAULTS.INI file of the EyeLink tracker, or may be sent
over the link.
recording_parse_type = <data type: one of PUPIL, HREF, or GAZE>
The data type used for parsing will always be included in the event data. Other
data reported for eye-movement events are controlled with the "file_event_data"
command. This is followed by a list of data types and options, selected from the
list below:
Keyword Effect
GAZE
includes display (gaze) position data
GAZERES includes units-per-degree screen resolution (for start, end of event)
HREF
includes head-referenced eye position
AREA
includes pupil area or diameter
VELOCITY includes velocity of parsed position-type (average, peak, start and
end)
STATUS includes warning and error flags, aggregated across event (not yet
supported)
FIXAVG include ONLY averages in fixation end events, to reduce file size
NOSTART start events have no data other than timestamp
The "file_event_data" command may be edited in the DATA.INI file of the
EyeLink tracker, or may be sent over the link. Some example settings are given
below:
