[FieldTrip] help SR_eyelink+eeg data processing

[Schoffelen, J.M. (Jan Mathijs)]

Hi Umberto,

Well, my suggestion would be to write some code that is properly dealing with the events in fieldtrip style, and add this code to ft_read_event.
Specifically, in the section of ft_read_event that deals with ‘eyelink_asc’ (line 1109 and beyond), add some code that deals with the relevant stuff that is present in hdr.orig.msg.

Rather than putting the events in a matrix, I’d put them in the same format as the typical events that fieldtrip can work with.

The way this is ideally done, is that you make the changes, and submit this changes (+an associated test script) as a so-called Pull Request on github. Some more information about our workflow can be found on https://www.fieldtriptoolbox.org/development/contribute/ (and in the links therein).

Best wishes,
Jan-Mathijs




On 19 Mar 2021, at 08:34, Cavallo, Umberto (Stud. FPN) <u.cavallo at student.maastrichtuniversity.nl<mailto:u.cavallo at student.maastrichtuniversity.nl>> wrote:

Thanks for the answer Jan,
Yes I tried with ft read event, and I’ve tried with all frieldtrip tutorial instructions, but the problem is that the only events detected without using the code I sent are the first and last time stamp, thus to get all the triggers I can’t use ft read event. The only way it works is by storing them in a matrix. Maybe there is a way sto take the matrix with the stored event and store it into a cfg that allows me to use ft functions. Any suggestion?
Best,
Umberto
________________________________
Da: fieldtrip <fieldtrip-bounces at science.ru.nl<mailto:fieldtrip-bounces at science.ru.nl>> per conto di Schoffelen, J.M. (Jan Mathijs) <jan.schoffelen at donders.ru.nl<mailto:jan.schoffelen at donders.ru.nl>>
Inviato: venerdì 19 marzo 2021 08:08:08
A: FieldTrip discussion list
Oggetto: Re: [FieldTrip] help SR_eyelink+eeg data processing

Ciao Umberto,

Have you tried ft_read_event?

See https://www.fieldtriptoolbox.org/getting_started/eyelink/

Good luck,

Jan-Mathijs


On 19 Mar 2021, at 06:42, Cavallo, Umberto (Stud. FPN) <u.cavallo at student.maastrichtuniversity.nl<mailto:u.cavallo at student.maastrichtuniversity.nl>> wrote:

Dear All,
i am doing an experiment in which i simultaneously acquire eeg data and SR eyelink eyetracker data.
I still do not have eeg data, but i am trying to analyse my eyedata with fieldtrip since i will need this when i will  have eeg data too.
Due to the acquisition method the only way in which i can read the triggers from the eyedata is the following:
cfg = [];
cfg.dataset = filename_eye;
cfg.montage.tra      = eye(4)
cfg.montage.labelorg = {'1', '2', '3', '4'};
cfg.montage.labelnew = {'EYE_sample_numbers', 'EYE_HORIZONTAL', 'EYE_VERTICAL', 'EYE_DIAMETER'}
data_eye= ft_preprocessing(cfg);
hdr = ft_read_header(filename_eye);
event=[];
for evt=1:size(hdr.orig.msg,1)
    tmp=hdr.orig.msg{evt};
    ix=find(tmp==' ');
    if length(ix)==1
        event=[event;str2num(tmp(5:ix(1)-1)), str2num(tmp(ix(1):end))];
    end
end

​basically all my events are stored in the matrix EVENT, and my eye data are stored in the structure data_eye.
I've tried to use built in functions to read events, however, they are not stored in cfg.event or anywhere else by using the classic fieldtrip functions. In fact, in this case the only event Fieldtrip read is the first timestamp and the last one, but not all the others.
Given that everything besides my events (and their triggers), which are stored in a matrix, are stored in data_eye, could you help me in finding a way to use the analysis functions of fieldtrip (like ft_timelockstatistics for data analysis).Or a way in which i can manipulate my data storage to use fieldtrip functions?
thanks in advance.
Best,
Umberto

_______________________________________________
fieldtrip mailing list
https://mailman.science.ru.nl/mailman/listinfo/fieldtrip
https://doi.org/10.1371/journal.pcbi.1002202

_______________________________________________
fieldtrip mailing list
https://mailman.science.ru.nl/mailman/listinfo/fieldtrip
https://doi.org/10.1371/journal.pcbi.1002202

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.science.ru.nl/pipermail/fieldtrip/attachments/20210319/c0364522/attachment.htm>