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 am having a problem with camera calibration for some sessions. The equivalent calibration procedure works for most sessions, but for some this error appears. I can not identify any significant difference in the calibration videos for this session in comparison to the ones without the error. I only see that for Cam_03 there are some NaNs in a matrix .... 'name': 'Cam_03', 'size': [1280, 1024], 'matrix': [[nan, 0.0, 639.5], [0.0, nan, 511.5], [0.0, 0.0, 1.0]] .... As you can see below there are plenty of board detection in this specific camera, so I am not sure what is causing this behavior.
Even though the error comes from rvecs, tvecs = get_initial_extrinsics(rtvecs, self.get_names()), it seems that the initialization of the intrinsics is to blame for this. I have found a workaround, which is to initialize CameraGroup from another session with a successful calibration and skip the intrinsics initialization (skipping just the extrinsics initialization doesn't solve the issue).
Here is a code snippet for this:
vonaviv
changed the title
Camera calibration fails due to NaNs in a camera matrix
[ Camera calibration ] NaNs in camera matrix after intrinsics initialization
Jan 22, 2025
Hello,
I am having a problem with camera calibration for some sessions. The equivalent calibration procedure works for most sessions, but for some this error appears. I can not identify any significant difference in the calibration videos for this session in comparison to the ones without the error. I only see that for
Cam_03
there are some NaNs in a matrix.... 'name': 'Cam_03', 'size': [1280, 1024], 'matrix': [[nan, 0.0, 639.5], [0.0, nan, 511.5], [0.0, 0.0, 1.0]] ...
. As you can see below there are plenty of board detection in this specific camera, so I am not sure what is causing this behavior.The text was updated successfully, but these errors were encountered: