Howdy, Stranger!

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

Supported by

eyelink fix_triggered_drift_correction()

edited July 2016 in PyGaze


I've noticed that using the eyelink, the fix_triggered_drift_correction() function does not actually perform a calibration if you press q/escape, it just returns false.

Is there some reason for this in PyGaze 0.4 such that I shouldn't fiddle w/ this? I notice that the development version corrects this problem. To your knowledge is it relatively safe to replace the 0.4 version of the function w/ the development version and/or just modify the code to trigger calibration myself?


Sign In or Register to comment.