Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report: Problem with E-Prime "offsets" + Eyelink #20

Open
olafdimigen opened this issue Jan 7, 2022 · 2 comments
Open

Bug report: Problem with E-Prime "offsets" + Eyelink #20

olafdimigen opened this issue Jan 7, 2022 · 2 comments

Comments

@olafdimigen
Copy link
Owner

Received the following bug report:

When we try to synchronize data in eeglab with eye-eeg, we found that messages could not be recognized from *.asc file. After lots of tests, finally we found that eye-eeg could not read messages with offset.

The full structure of Eyelink messages is:

`‘MSG' + timeStamp + [offset] + messageText`

Messages with [offset] means events happened [offset] millisecond ago. Like this:

`MSG	4336690 3151 face2_Onset 127`

And those without [offset] means events happens realtime. Like this(4333539 = 4336690 - 3151):

`MSG	4333539	face2_Onset 127`

Messages with [offset] are used in E-Prime to markup the actually onset time of each E-Object(stimulate screen).

@olafdimigen
Copy link
Owner Author

olafdimigen commented Jan 8, 2022

need to adapt regexp in parseeyelink.m

timestamps = regexp(tmp,'^-?\D+(\d+)','tokens','once','lineanchors');

@olafdimigen olafdimigen changed the title Bug report: Problem with E-Prime + Eyeline Bug report: Problem with E-Prime "offsets" + Eyelink Jan 17, 2022
@olafdimigen
Copy link
Owner Author

open question: how to differentiate cases with an offset from messages containing one or more integers as their user-defined "content"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant