# Eyelink output

**URL:** <https://mworks.discourse.group/t/eyelink-output/562>\
**Category:** Support\
**Created:** [September 15, 2014, 1:42pm UTC](https://mworks.discourse.group/t/eyelink-output/562 "2014-09-15T13:42:19Z")\
**Posts on this page:** 8\
**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 15, 2014, 1:42pm UTC](https://mworks.discourse.group/t/eyelink-output/562/1 "2014-09-15T13:42:19Z")

</div>

Hi Chris,

I noticed that the signal that I’m getting from Eyelink doesn’t change when I adjust the calibration in the Eyelink system, which makes me think I’m getting the “raw” signal rather than “gaze,” which is what I want. Do you know which (if any) of the Eyelink object parameters represent calibrated gaze data? The full list of options are:

eye\_rx  
eye\_ry  
eye\_lx  
eye\_ly  
eye\_x  
eye\_y  
eye\_z  
href\_rx  
href\_ry  
href\_lx  
href\_ly  
pupil\_rx  
pupil\_ry  
pupil\_lx  
pupil\_ly  
pupil\_size\_r  
pupil\_size\_l

- Evan

---

<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 15, 2014, 3:06pm UTC](https://mworks.discourse.group/t/eyelink-output/562/2 "2014-09-15T15:06:04Z")

</div>

Hi Evan,

As far as I can tell, MWorks isn’t getting any uncalibrated data from the EyeLink. However, you do have a choice between “gaze” (described in the EyeLink manual as “screen gaze x, y”, which “reports the actual (x, y) coordinates of the subject’s gaze on the display, compensating for distance from the display”) and “HREF” (“head referenced-calibrated x, y”, which “directly measures eye rotation angles relative to the head”). Gaze is reported via eye\_rx, eye\_ry, eye\_lx, eye\_ly; HREF goes to href\_rx, href\_ry, href\_lx, href\_ry. It seems like both sets of data should be calibrated, but it might be worth testing both.

As for the other options, eye\_x, eye\_y, eye\_z are the 3-D gaze coordinates, as computed by the MWorks plugin using the left and right gaze data and tracking\_dist. The pupil-related variables report “camera X, Y of pupil center”, which I’m guessing would not be useful to you.

Cheers,  
Chris

---

<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 15, 2014, 4:47pm UTC](https://mworks.discourse.group/t/eyelink-output/562/3 "2014-09-15T16:47:49Z")

</div>

Hi Chris,

I spoke with William Schmidt from SR Research, he says that if we want to  
use the particular type of calibration that we’d like, we need to be  
looking at the “raw” signal, which should be available in the link data  
stream. Can we get the raw outputs included in the Eyelink object?

Thanks,

- Evan

---

<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 15, 2014, 6:49pm UTC](https://mworks.discourse.group/t/eyelink-output/562/4 "2014-09-15T18:49:33Z")

</div>

Hi Evan,

> if we want to use the particular type of calibration that we’d like, we need to be looking at the “raw” signal, which should be available in the link data stream.

After further investigation, I think I was wrong: It looks like pupil\_rx, pupil\_ry, pupil\_lx, and pupil\_ly _do_ provide the “raw” signal you want. From the EyeLink user manual:

> Pupil position data is raw (x, y) coordinate pairs from the camera. It has not been converted to eye angles or to gaze position. There may be a non-linear relationship between this data and true gaze position. Pupil position is reported in integer values, with 200 to 400 units per visual degree.
> 
> When a calibration has not been performed, the EyeLink system cannot convert pupil data to the more useful data types. Raw pupil position is useful when auto-sequencing calibrations, or when the application wishes to perform its own calibration.

Does that sound like what you need? If so, it’s already available via the pupil\_\* outputs.

Chris

---

<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 15, 2014, 8:24pm UTC](https://mworks.discourse.group/t/eyelink-output/562/5 "2014-09-15T20:24:48Z")

</div>

Hi Chris,

We just tried this (moved the eye position variables from eye\_\* to pupil\_\*)  
and the value of the MWorks variables become static (i.e. pegged at ~2^15).  
Are you sure the raw input has been implemented in MWorks?

- Evan

---

<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 16, 2014, 2:04pm UTC](https://mworks.discourse.group/t/eyelink-output/562/6 "2014-09-16T14:04:40Z")

</div>

Hi Evan,

> We just tried this (moved the eye position variables from eye\_\* to pupil\_\*) and the value of the MWorks variables become static (i.e. pegged at ~2^15). Are you sure the raw input has been implemented in MWorks?

It certainly _looks_ like it’s implemented. If the EyeLink weren’t sending pupil positions, then the pupil\_\* variables would be set to -32768. You’re not seeing that, which suggests the EyeLink is sending MWorks _something_.

I have no idea if this matters or not, but I did notice just recently that SR Research published new [drivers for OS X]([SR Support Forum](https://www.sr-support.com/showthread.php?15-EyeLink-Developers-Kit-for-Mac-OS-X-(Mac-OS-X-Display-Software)) in July. Do you want to install those and see if it makes any difference?

If that doesn’t help, then I’ll need to try debugging with the real hardware.

Chris

---

<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 16, 2014, 7:07pm UTC](https://mworks.discourse.group/t/eyelink-output/562/7 "2014-09-16T19:07:18Z")

</div>

Hi Evan,

As we discussed offline, the problem was that MWorks needed to tell the EyeLink (via the `link_sample_data` command) to include pupil coordinates in the eye data. This change will be in tonight’s nightly build.

Cheers,  
Chris

---

<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:58pm UTC](https://mworks.discourse.group/t/eyelink-output/562/8 "2022-07-19T22:58:05Z")

</div>

Closed on July 19, 2022, 10:58pm UTC


