User manual

Data Files
© 2005-2008 SR Research Ltd.
99
4.6.1 Sample Data
The sample data written to the EDF file is controlled by the "file_sample_data"
command, which is followed by a list of data types to include. A single keyword
is included for each type:
Keyword Data Type
LEFT,
RIGHT
Sets the intended tracking eye (usually include both LEFT and…
RIGHT)
GAZE includes screen gaze position data
GAZERES includes units-per-degree screen resolution at point of gaze
HREF
HTARGET
head-referenced eye position data
target distance and X/Y position (EyeLink Remote only)
PUPIL raw pupil coordinates
AREA pupil size data (diameter or area)
BUTTON buttons 1-8 state and change flags
STATUS warning and error flags (not yet supported)
INPUT input port data lines (not yet supported)
The default data is:
file_sample_data = LEFT,RIGHT,GAZE,GAZERES,AREA,STATUS
Usually, data for both eyes is enabled, and the menus in the EyeLink 1000
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:
file_sample_data = LEFT,RIGHT,GAZE,GAZERES,HTARGET,AREA,STATUS
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 1000 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"