Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

trial duration discrepancy in eyelink data

I'm doing a simple dot probe task. My trials are 2500ms long, using sketchpad for the fixation, images, and probe events nested between pygaze_start_recording and pygaze_stop_recording. I have confirmed that when the task runs it is indeed 2500ms long, yet my eyelink data files show trial durations of ~3275. I have played around with different event lengths, but no matter what, there seems to be an extra ~775ms in each eyelink recording.

Any ideas about the source of this extra time?

Comments

  • After playing around with variations of the design, I'm finding that what's most likely happening is around ~375ms of delay between the start of recording and the onset of first event, and the rest of the time is a delay between logging events and stopping recording.

Sign In or Register to comment.