# Eyelink data timing

**URL:** <https://mworks.discourse.group/t/eyelink-data-timing/555>\
**Category:** Support\
**Created:** [September 22, 2014, 8:48pm UTC](https://mworks.discourse.group/t/eyelink-data-timing/555 "2014-09-22T20:48:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)\
**Post date:** [September 22, 2014, 8:48pm UTC](https://mworks.discourse.group/t/eyelink-data-timing/555/1 "2014-09-22T20:48:37Z")

</div>

I have an Eyelink system set up to sample eye position at 1000 Hz. Looking at the MWorks event data, I have many (~5%) successive raw eye position updates with time differences of less than 500 microseconds. Inspecting the interval histogram shows a small peak around 50 us. I’ve read the timestamping article in the knowledge base, and I’m not sure what could be causing this.

---

<div class="post-metadata">

**Author:** ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)\
**Post date:** [July 19, 2022, 10:57pm UTC](https://mworks.discourse.group/t/eyelink-data-timing/555/2 "2022-07-19T22:57:11Z")

</div>