You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently come across a tiny, but troublesome error: if you calibrate the Gazepoint eye-tracker, it works like a charm. However, if you recalibrate the device (i.e. by pressing 'q' during the validation), the final calibration point is 'missing' (well, it's not technically missing, it's just not shown). Instead of moving to the final position, the red circle just stays in the second-to-last position, of course resulting in funny calibration results, unless you keep track of the positions and know exactly where to look for the last one. I could probably fix it myself in the opengaze script, but someone else might face the same problem one day, which is why I'm reporting it here :)
Thanks in advance!
The text was updated successfully, but these errors were encountered:
That's an interesting issue! I can't say I've encountered it in a while. Could you confirm that you are both on the latest PyGaze code (i.e. the stuff you can download from the master branch on GitHub), and that you're using the latest version of GazePoint's software?
According to OpenSesame's package manager, pygaze is the indeed the latest version (0.6.0a25). I'm also using the most current version of GazePoint's software :)
Hi Edwin,
I've recently come across a tiny, but troublesome error: if you calibrate the Gazepoint eye-tracker, it works like a charm. However, if you recalibrate the device (i.e. by pressing 'q' during the validation), the final calibration point is 'missing' (well, it's not technically missing, it's just not shown). Instead of moving to the final position, the red circle just stays in the second-to-last position, of course resulting in funny calibration results, unless you keep track of the positions and know exactly where to look for the last one. I could probably fix it myself in the opengaze script, but someone else might face the same problem one day, which is why I'm reporting it here :)
Thanks in advance!
The text was updated successfully, but these errors were encountered: