-
Notifications
You must be signed in to change notification settings - Fork 679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gazer2D calibration data(errorlines/convex hull) no longer displayed. #2321
Comments
does not happen with python3.9. so that seems related to the difference in |
However, it seems that |
Hi. @bpinsard ! Thanks for reporting it. Would you mind clarifying whether you are running it from source or from the bundle? |
Yes running from source, from master branch. |
Hi! We recommend installing it from the bundle unless strictly necessary (i.e. because you want to modify some parts of the source code). Is that the case? Otherwise, you can install it by downloading the precompiled version from Releases. When running from the source, we recommend using the With that said, the master branch already has some changes that are coming with release 3.6 (not yet released). See MR at commit 5e678b7 We did not finalise the release, so you can roll back your local version to a previous commit and run it from there or ride wild with us 😉 .
|
In past versions, there was a bunch of orange lines in the world window + convex hull that were displayed when completing a calibration.
It's no longer the case in the master branch in my conditions (do not have pupil hardware to test).
I am sending calibration data through the IPC backbone for tests with smthg like :
The calibration is successful, but nothing is displayed in the world window, (was working in anterior versions).
When I changed that line https://github.com/pupil-labs/pupil/blob/master/pupil_src/shared_modules/gaze_mapping/notifications.py#L50 to except only
AssertionError
, I get the following traceback.So the Gazer2D notification is silently dismissed and never processed by the AccuracyVisualizer, hence the absence of display.
The particular value of the notification that seems to trigger that exception during unserialization is
gazer_class_name:Gazer2D
I am not sure what exactly changed in the code to cause that issue and I am not exactly sure how it can be fixed.
env: python3.8.10 on linux
The text was updated successfully, but these errors were encountered: