esdalmaijer / PyTribe

Python wrapper for the EyeTribe SDK
GNU General Public License v3.0
27 stars 18 forks source link

bug in restart calibration Pytribe #4

Open dvanmoorselaar opened 9 years ago

dvanmoorselaar commented 9 years ago

Hello,

It seems there is a bug in calibration procedure. After running calibration, the output tells whether calibration is succesfull or whether it failed. You then have the option to continue (press space) or restart the calibration (R). In case of a failed calibration it is not possible to restart (R) the calibration as an error pops up that calibration is allready in progress. The surprising thing is that in case of a succesfull calibration you can restart the calibration without any problems. See the traceback of the error below:

Unexpected error line: 1127 exception message: Error in calibration.start: Calibration already in progress (code 403) exception type: Exception

Traceback (also in debug window): File "dist\libqtopensesame\misc\process.py", line 139, in run File "dist\libopensesame\experiment.py", line 344, in run File "dist\libopensesame\sequence.py", line 47, in run File "C:\Program Files (x86)\OpenSesame\plugins\pygaze_init\pygaze_init.py", line 208, in run File "dist\pygaze_eyetracker\libeyetribe.py", line 192, in calibrate File "dist\pygaze_eyetracker\pytribe.py", line 1127, in start Exception: Error in calibration.start: Calibration already in progress (code 403)

Best,

Dirk van Moorselaar

ArshamSol commented 8 years ago

Hi could you help me how can i run calibration ? I have the error "Calibration already in progress" when I call tracker.calibration.start(). this is traceback of error : File "E:/Code/EyeTracking/PyTribe-master/example/experiment.py", line 78, in tracker.calibration.start(9) File "E:\Code\EyeTracking\PyTribe-master\pytribe.py", line 1126, in start raise Exception("Error in calibration.start: %s (code %d)" % (response['values']['statusmessage'],response['statuscode'])) Exception: Error in calibration.start: Calibration already in progress (code 403)

esdalmaijer commented 8 years ago

Would you be able whether this bug still persist if you download the latest version? It should be fixed there. Thanks for flagging it up!