-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
need to adapt regexp in parseeyelink.m
|
olafdimigen
changed the title
Bug report: Problem with E-Prime + Eyeline
Bug report: Problem with E-Prime "offsets" + Eyelink
Jan 17, 2022
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
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:
Messages with [offset] means events happened [offset] millisecond ago. Like this:
And those without [offset] means events happens realtime. Like this(4333539 = 4336690 - 3151):
Messages with [offset] are used in E-Prime to markup the actually onset time of each E-Object(stimulate screen).
The text was updated successfully, but these errors were encountered: