| title | tags | ||||||
|---|---|---|---|---|---|---|---|
Converting an example eyetracker dataset for sharing in BIDS |
|
{% include markup/danger %} The BIDS standard does currently not specify how to represent eye tracker data. This example - and the support that is implemented in the data2bids function - should be considered as a preliminary proposal to help researchers with their existing data. This example may also serve to start a discussion on whether and how this data type should be added to the BIDS specification. {% include markup/end %}
Eye tracking data can be stored in the BIDS representation similar to behavioral data. This not only includes the gaze position, pupil diameter, but also allows for presentation (stimulus and response events) and saccades to be represented in the events.tsv file.
Rather than storing the eye tracker data as generic pysiological data in the _pysio.tsv file, the implementation of data2bids allows it to be specified as eyetracker data, resulting it to be written in an _eyetracker.tsv file, with an associated _eyetracker.json file with metadata details on the equipment and experiment.
{% include markup/info %} Information that need to be further considered to be documented in the metadata is for example whether both eyes or only one was tracked, sapling rate, if and how pupil diameter is quantified, what calibration process was used, how to interpret the gaze position (pixels, degrees), whether the origin is at the center of the screen or the upper left corner, etc. {% include markup/end %}
If the online analysis in the eye tracker software also detects blinks, saccades, and other events with a distinct time (i.e. non-continuous), those can also be added to the _events.tsv file.
{% include markup/success %} All data for the following examples is available from our download server. {% include markup/end %}
The examples includes the original log files under the “original” directory. It also has a copy of the script to do the conversion under “code”. The reorganized data is under the “bids” directory. According to the documentation the original data can be added to the BIDS dataset under the “sourcedata” directory and code can be added to the “code” directory. This way no information is lost and the conversion/reorganization is fully reproducible.
In general: if your original data is in a different format than the BIDS representation (e.g., DICOM instead of NIFTI, or the original binary data from the eye tracker software), you probably want to keep a copy of the original data as well, e.g., on a data acquisition collection on the Donders Repository. If it is in the same format (which is not the case here), you could simply delete the original data after conversion. In either case - your own analyses and the shared data would be based on the BIDS representation.
There are numerous eye tracking systems, such as SR Research EyeLink, Tobii, EyeTech, GazePoint, SmartEye and Pupil Labs. We cannot provide examples for all of them, but in principle data from each system would be stored in the same standard BIDS representation, allowing it to be reused by others.
{% include markup/info %} There is a draft BIDS extension proposal (BEP) to extend the specification with eye tracker data, you can find the discussion on google docs. {% include markup/end %}
The SR Research EyeLink system records the data in a binary file with the extension .edf. This is not to be confused with the European Data Format (https://www.edfplus.info) for EEG and other biological and physical signals. The proprietary EyeLink edf format cannot be read in open source software, but SR Research provides a tool called edf2asc.exe that converts the data to ASCII format. The ASCII format is still difficult to work with and represents a mixture of continuous gaze and pupil diameter parameters with discontinuous events, such as fixation, loss of tracking, etc.
FieldTrip can read the EyeLink .asc format. The gaze and/or pupil diameter are represented as continuous raw channels (accessible using ft_read_data and ft_preprocessing), the other information is represented as events (using ft_read_event and ft_definetrial). For more details you can see this page. In the examples below we use data2bids to read the .asc files and convert the data to a simple _eyetracker.tsv file for the continuous gaze and pupil diameter, and an _events.tsv file for the discontinuous events.
%% this is an example with a short calibration recording
% the same data is converted multiple times to demonstrate the directory layout and the participants
cfg = [];
cfg.InstitutionName = 'Radboud University';
cfg.InstitutionalDepartmentName = 'Donders Institute for Brain, Cognition and Behaviour';
cfg.InstitutionAddress = 'Kapittelweg 29, 6525 EN, Nijmegen, The Netherlands';
% required for dataset_description.json
cfg.dataset_description.Name = 'Eyelink example';
cfg.dataset_description.BIDSVersion = 'unofficial extension';
% optional for dataset_description.json
cfg.dataset_description.License = 'n/a';
cfg.dataset_description.Authors = 'n/a';
cfg.dataset_description.Acknowledgements = 'n/a';
cfg.dataset_description.Funding = 'n/a';
cfg.dataset_description.ReferencesAndLinks = 'n/a';
cfg.dataset_description.DatasetDOI = 'n/a';
cfg.method = 'convert'; % the eyelink-specific format is not supported, convert it to plain TSV
cfg.dataset = './original/ashcal.asc';
cfg.bidsroot = './bids'; % write to the working directory
cfg.datatype = 'eyetracker';
cfg.task = 'calibration';
% this is general metadata that ends up in the _eyetracker.json file
cfg.TaskDescription = 'Short calibration procedure';
cfg.Manufacturer = 'SR Research';
cfg.ManufacturerModelName = 'Eyelink 1000';
% convert the data from the first (and only one) subject
cfg.sub = '01';
cfg.participants.age = 23;
cfg.participants.sex = 'M';
data2bids(cfg);
% convert the same data again, pretending that it is subject 2
cfg.sub = '02';
cfg.participants.age = 25;
cfg.participants.sex = 'F';
data2bids(cfg);
% convert the same data again, pretending that it is subject 3
cfg.sub = '03';
cfg.participants.age = 31;
cfg.participants.sex = 'M';
data2bids(cfg);
%% this section specifies the data files
filename = {
'1_TO_1.asc'
'1_TO_2.asc'
'2_FH_1.asc'
'2_fh_2.asc'
'3_ac_1.asc'
'3_ac_2.asc'
'4_ym_1.asc'
'4_ym_2.asc'
'5_kj_1.asc'
'5_kj_2.asc'
'6_BS_1.asc'
'6_BS_2.asc'
'7_aa_1.asc'
'7_aa_2.asc'
'8_SG_1.asc'
'8_sg_2.asc'
'9_TE_1.asc'
'9_TE_2.asc'
'9_te_11.asc'
'10_es_1.asc'
'10_es_2.asc'
'11_AR_1.asc'
'11_AR_2.asc'
'12_LK_1.asc'
'12_LK_11.asc'
'12_LK_2.asc'
'12_LK_22.asc'
'13_JL_1.asc'
'13_JL_2.asc'
'14_vs_1.asc'
'14_vs_2.asc'
'15_CL_1.asc'
'15_CL_2.asc'
'16_MN_1.asc'
'16_MN_2.asc'
'17_NT_1.asc'
'17_NT_2.asc'
'18_CL_11.asc'
'18_CL_2.asc'
'19_AE_1.asc'
'19_AE_2.asc'
'20_AK_2.asc'
'20_PK_1.asc'
'21_SY_1.asc'
'21_SY_2.asc'
'22_VG_1.asc'
'22_VG_21.asc'
'22_VG_22.asc'
'23_DK_2.asc'
'23_dk_1.asc'
'24_TS_1.asc'
'24_TS_2.asc'
};
% The filenames have a sequence number and a two-letter subject identifier in them. The case of the
% identifier is not totally consistent. Furthermore, some subjects have two, some
% have three recordings.
sourcepath = './original/ascData';
targetpath = './bids';
%% find the unique subject identifiers
subjid = {};
for i=1:numel(filename)
part = split(filename{i}, '_');
subjid{end+1} = upper(part{2});
end
subjid = unique(subjid, 'stable'); % keep them in the original order
%% loop over subjects and convert the datafiles for each subject
cfg = [];
cfg.InstitutionName = 'Radboud University';
cfg.InstitutionalDepartmentName = 'Donders Institute for Brain, Cognition and Behaviour';
cfg.InstitutionAddress = 'Kapittelweg 29, 6525 EN, Nijmegen, The Netherlands';
% required for dataset_description.json
cfg.dataset_description.Name = 'Visual Stability: predictive remapping of features beyond saccadic targets';
cfg.dataset_description.BIDSVersion = 'unofficial extension';
% optional for dataset_description.json
cfg.dataset_description.Authors = 'Tao He, Matthias Fritsche, Floris de Lange';
cfg.dataset_description.DatasetDOI = 'http://hdl.handle.net/11633/di.dccn.DSC_3018034.01_694';
cfg.dataset_description.License = 'RU-DI-HD-1.0';
cfg.dataset_description.Acknowledgements = 'n/a';
cfg.dataset_description.Funding = 'n/a';
cfg.dataset_description.ReferencesAndLinks = 'n/a';
for i=1:numel(subjid)
fileselection = find(contains(filename, ['_' subjid{i} '_'], 'IgnoreCase', true));
for j=1:numel(fileselection)
[p, f, x] = fileparts(filename{fileselection(j)}); % split the path, filename and extension
part = split(f, '_'); % split the filename
run = str2double(part{3});
% this is the data in ASCII format
cfg.dataset = fullfile(sourcepath, [f x]);
cfg.method = 'convert';
% these are used to construct the directory and file name
cfg.bidsroot = targetpath;
cfg.datatype = 'eyetracker';
cfg.sub = subjid{i};
cfg.run = run;
cfg.task = 'adaptation';
% this is additional information that ends up in the sidecar JSON file
cfg.TaskDescription = 'orientation adaptation paradigm';
data2bids(cfg);
end % for fileselection
end % for subjid
The SMI eye tracker stores the raw data in an .idf file. That file cannot be read (easily) with other analysis software, hence the SMI specific IDF converter program from the iView tools needs to be used to convert it to ascii. Please note that this is Windows software that comes with the eye tracker. At the DCCN you can ask Paul for more details on the SMI eye trackers.
In the following example we are converting two runs of eye tracker data for two subjects. The data was recorded at the DCCN. Since additional information is missing (e.g., units, origin, calibration procedure), the metadata is very sparse.
filename = {
'original/pp23671_rest1_samples.txt'
'original/pp23671_task1_samples.txt'
'original/pp31237_rest1_samples.txt'
'original/pp31237_task1_samples.txt'
};
% note that the original filename includes the subject identifier and the task
% these are used further down and included in the output
cfg = [];
cfg.InstitutionName = 'Radboud University';
cfg.InstitutionalDepartmentName = 'Donders Institute for Brain, Cognition and Behaviour';
cfg.InstitutionAddress = 'Kapittelweg 29, 6525 EN, Nijmegen, The Netherlands';
% required for dataset_description.json
cfg.dataset_description.Name = 'SMI example';
cfg.dataset_description.BIDSVersion = 'unofficial extension';
% optional for dataset_description.json
cfg.dataset_description.License = 'n/a';
cfg.dataset_description.Authors = 'n/a';
cfg.dataset_description.Acknowledgements = 'n/a';
cfg.dataset_description.Funding = 'n/a';
cfg.dataset_description.ReferencesAndLinks = 'n/a';
cfg.dataset_description.DatasetDOI = 'n/a';
cfg.Manufacturer = 'SMI';
cfg.ManufacturerModelName = 'iView X MRI-LR';
cfg.method = 'convert'; % the SMI-specific format is not supported, convert it to plain TSV
cfg.bidsroot = './bids'; % write to the working directory
cfg.datatype = 'eyetracker';
for i=1:4
cfg.dataset = filename{i};
% split the filename to get the subject identifier and the task
[p, f, x] = fileparts(filename{i});
piece = split(f, '_');
cfg.sub = piece{1};
cfg.task = piece{2};
data2bids(cfg);
end
The data from the TOBII eye tracker can be exported in .tsv or in .xlsx format. Moreover, the data can be exported to either have a file for each subject, or with all the subjects in one file. Both formats are included in the example. The TOBI studio software allows to add additional information in the exported files.