If you are asking just how to mechanically line up E-Prime data with
eye-tracker data after the fact during data processing (e.g., with
Excel), then I have nothing to add.
If you are asking how generate data during the session in order to
translate timestamps between E-Prime & eye-tracker ... I ran across
this very problem awhile ago when using E-Prime in conjunction with an
Arduino. I solved it the same way that I would solve it with people --
I look at my watch, ask my companion what time they have on their watch,
and write down both times. Thereafter I can translate times from one
watch into times for the other.
So with two electronic devices (e.g., E-Prime vs. eye-tracker or
Arduino), Device A records its own time, and immediately also gets the
time from Device B. If you want to compensate for communication delays,
Device A records its own time both just before and just after it gets a
timestamp from Device B, and then considers the Device B timestamp to be
equal to the average of Device A's before & after timestamps. It does
not matter whether Device A is E-Prime or the external device, and
vice-versa (in my case, E-Prime requested the time from the Arduino).
(This all assumes, of course, that the clocks on both devices keep
proper time except for a constant offset -- otherwise, you might do a
synchronization both at the start and at the end of the session, and
then do a linear interpolation for times in between.)
Most likely people who do serious timekeeping among multiple devices
have long ago solved this problem, and it would be interesting to learn
from them. But this is my hacked-out solution.
-- David McFarlane