I'm using the surface tracker plugin on the pupil core software. Ive physically added legacy square markers to the edge of the bezel on my mac. The surface tracker plugin detects markers on the screen. After the surface is added, there are parameters for width and height, by default 1.0. Do I have to physically calculate the distance between the markers and change the width and height?
The problem I'm trying to solve is this: I'm recording the surface area, and I want where my gaze is at on the surface, but in pixel corrdinates, instead of norm_pos. How do I achieve it?
@user-2386d5 Pixel coordinate systems usually have their origin in the top left. Is this the case for your target coordinate system as well?
Yes it's the same for the target coordinate system.
Ok, then in this case, setting the surface side will only help you partially since norm_pos has its origin in the bottom left
You will have to manually transform the norm_pos into pixel locations using this formular:
pixel_x = int(norm_pos_x * pixel_width)
pixel_y = int((1.0 - norm_pos_y) * pixel_height)
See https://docs.pupil-labs.com/core/terminology/#coordinate-system for reference
And this should work as is because world image to surface transformation has already being done right? If that's the case, this is what I'd be doing since I saw one of the tutorials you wrote.
Hello, I am feeding eye0 video using pupil video backend service from here https://github.com/Lifestohack/pupil-video-backend.
I use raspberry pi camera as eye0 to feed the gray frames from pupil-video-backend. That means the video feed for eye0 is coming from raspberry pi wirelessly over wifi. The world camera is directly connected to my computer. Now i want to calibrate it but every time I want to calibrate it says calibration failed. Eye0 has detected the pupil and has confidence of 1.0
My eye0 is little bit dark as I am using only one ir led. But it should not be the problem or? I have already the confidence level of 1.
2020-12-11 19:41:40,125 - world - [INFO] calibration_choreography.base_plugin: Starting Calibration
2020-12-11 19:41:40,297 - world - [DEBUG] calibration_choreography.screen_marker_plugin: Moving screen marker to site at (0.5, 0.5)
2020-12-11 19:41:42,874 - world - [DEBUG] calibration_choreography.screen_marker_plugin: Moving screen marker to site at (0.0, 1.0)
2020-12-11 19:41:45,238 - world - [DEBUG] calibration_choreography.screen_marker_plugin: Moving screen marker to site at (1.0, 1.0)
2020-12-11 19:41:47,870 - world - [DEBUG] calibration_choreography.screen_marker_plugin: Moving screen marker to site at (1.0, 0.0)
2020-12-11 19:41:50,248 - world - [DEBUG] calibration_choreography.screen_marker_plugin: Moving screen marker to site at (0.0, 0.0)
2020-12-11 19:41:52,895 - world - [INFO] calibration_choreography.base_plugin: Stopping Calibration
2020-12-11 19:41:52,926 - world - [WARNING] calibration_choreography.base_plugin: Calibration already stopped.
2020-12-11 19:41:52,935 - world - [INFO] gaze_mapping.utils: Dismissing 6.32% pupil data due to confidence < 0.80
2020-12-11 19:41:52,938 - world - [DEBUG] gaze_mapping.utils: Collected 0 binocular references.
2020-12-11 19:41:52,938 - world - [DEBUG] gaze_mapping.utils: Collected 0 right eye monocular references.
2020-12-11 19:41:52,938 - world - [DEBUG] gaze_mapping.utils: Collected 0 left eye monocular references.
2020-12-11 19:41:52,938 - world - [ERROR] gaze_mapping.gazer_base: Calibration Failed!
2020-12-11 19:41:52,938 - world - [ERROR] gaze_mapping.gazer_base: Not sufficient data available.
2020-12-11 19:41:52,939 - world - [WARNING] plugin: Plugin Gazer3D failed to initialize
@user-d8853d Your eye and world video seem to follow different time epochs. IN other words, the time disparity between pupil and reference data is too large to build pairs. Make sure the time sync works as expected.
@papr thanks. Jeah that was the problem.
what to do with the driver change the USB camera ZADIG-2.4 ?
Could you please provide more context? I am not sure what problem you are trying to solve.