You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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: