[open] Eyelink, measuring saccade latencies with a script
We are facing a problem concerning the real-time use of eyelink data in an experiment. What we would like to do is to monitor saccade latencies in one condition and then use that information in another condition. Actually pretty similar to one of your examples, the curvature demo;)
However, the latency information we acquire that way does not exactly seem to match with the data we get out of the edf-file. Also, we sometimes get strange latencies of 0ms, while there was nothing wrong with the saccade as it turned out in the edf-file.
So we were wondering whether monitoring eyelink samples within a loop (or for instance using the wait_for_fixation_end function) just gives slightly different (shorter) latencies than those you would get watching individual trials with eyelink's data-viewer. Or do you think we could have done something wrong?
And out of mere interest, could you perhaps explain a little bit more about how the wait_for_fixation_end function works?
Thanks a lot!
(OpenSesame is great though!)