Hello. Currently I'm using mac and try to run Pupil from Source, and get this error "Could not build wheels for av". Here is the log file. May I ask how this issue caused? Thanks!

Then there are wheels for all dependencies

Thanks for noticing! Currently using Conda for virtual environment

Thank you so much!!

I made it work yesterday! The frame rate seems locked at 30fps

HD-6000

Haven’t removed the case yet. Just a initial test.

Oki

Yeah, still looking for another hd-6000 haha. Btw, I also saw some camera module OV9281 online. Maybe it’s perfect for this use case too

Hello, I'm using Pupil Invisible to detect the blinks and I would like to export the frames of the video "world" when the eyes are closed. So I installed Blink Detector (https://github.com/pupil-labs/pupil/blob/master/pupil_src/shared_modules/blink_detection.py) on Pupil Player. And it seems that the plug-in doesn't work with the blinks.csv file. And I've found the plugin Post hoc blink detection, but I don't know if it allow me to export the images of the world video during the blink https://gist.github.com/papr/40ba7d99f572bc0fe388a81aa2f87424.

Never the less, even the Post hoc blink dectection allow me to do this. I've problem to make it works correctly. I've ERROR message : player - [WARNING] plugin: Failed to load 'batch_exporter'. Reason: 'No module named 'exporter'' player - [WARNING] plugin: Failed to load 'extract_blinks'. Reason: 'No module named 'pandas'' But I've already installed exporter and pandas on my computer...

Does anyone have an idea to solve those problems ? I'm not devlopper and I don't know python, so that's part of the problem. But if any of you have a teacher soul and the patience to help me it could be nice.

Hey @user-e3f20f , I believe that pye3d uses optimization (ceres solver) to fit the 3D eye model. Can you point me to where this happens in the pye3d package?

...and is the optimization of reprojection error?

For some context, we've now played enough with the entire pipeline to develop the strong opinion that this is the step that's contributing the majority of error. Not the binocular model fit.

Not pupil detection.

(although that may be a related issue, our models aren't improving things)

That was only the case for the old 3d detector. Pye3d performs a closed-form optimization.

By binocular model fit you are referring to the gaze calibration?

That's the closed Form optimization

One more idea to drop ...

We've found that the precision of the final gaze estimate is relatively poor when the model is not frozen. The high-frequency sample-to-sample updating seems to be the issue. We could play with the paramters and calm it, perhaps, but my first inclination is that the updates should not be applied directly to the 3D eye pose center.

Instead, I would consider applying them to an attractor towards which the eyeball center accelerates.

perhaps in a PD-controller-like fashion. This is just one of many possible ways to low-pass filter those updates.

Ah, that's interesting. I'll have to look into that a bit more closely.

Hello, is it possible to plot x,y coordinate on the screen from norm_pos_x and norm_pos_y?

hey @user-e3f20f thanks for your quick response on github. I just installed C-Make version 3.25 (via snap) and still unable to build pyuvc 😦

I think the current error is:|

`CMake Error at CMakeLists.txt:103 (target_link_libraries): Target "uvc_bindings" links to:

  PLLibUVC::uvc

but the target was not found.  Possible reasons include:

`

Thanks!

So out of 'norm_pos_x', 'norm_pos_y', 'gaze_point_3d_x', 'gaze_point_3d_y', 'gaze_point_3d_z', 'eye_center0_3d_x', 'eye_center0_3d_y', 'eye_center0_3d_z', 'eye_center1_3d_x', 'eye_center1_3d_y', 'eye_center1_3d_z', 'gaze_normal0_x', 'gaze_normal0_y', 'gaze_normal0_z', 'gaze_normal1_x', 'gaze_normal1_y', 'gaze_normal1_z', 'diameter0_2d', 'diameter1_2d', 'diameter0_3d', 'diameter1_3d' can I use anything to plot x,y coordinate on the screen? Any help would be appreciated.

Well not really! I have screenshots and I wanted to overlay dots showing where the subject was looking at!

I have POV view as well from the main camera of pupil capture. Can I use that overlay dots on the screenshot showing where the subject was looking at?

By POV I mean this!

I see. So technically speaking there is no workaround for what I want to do?

There is, but you need to use the surface tracking.

In this case, if I understood your current situation correctly, there is no easy way to map the gaze from POV into screenshot coordinates, sorry. 😕

If ones does, then the surfaces.pldata file. But that sounds as if your recordings do include surface tracking data. Have you reviewed the recording in Player to check?