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
We think the issue is related to the resolution of the camera.
On my laptop, where the bug did not happen, the resolution of the imshow was wrong.
It looks like the solvePnP complications are all done on the assumption that it's a 480x480 camera.
There are also some issues with different versions of openCV not working the same way. When running on the desktop, we never had to configure the resolution of the camera manually, but on the BeagleBone, we had to configure that just to get it to run.
It looks like there are still some configuration settings that we're not setting.
The text was updated successfully, but these errors were encountered:
If you are using 2 different versions of OpenCV, you need to write the version specific code in an if statement and check against the modules version variable.
So using the
solvePnP
technique, we are getting incorrect values for the XYZ vector from the camera to the code.This only happens on some computers. It happens on the BeagleBone, and on @BrettGoldbach Ubuntu laptop, but not on my fedora laptop.
Recalibrating the camera helped a little bit but not a lot.
We think the issue is related to the resolution of the camera.
On my laptop, where the bug did not happen, the resolution of the imshow was wrong.
It looks like the
solvePnP
complications are all done on the assumption that it's a 480x480 camera.There are also some issues with different versions of openCV not working the same way. When running on the desktop, we never had to configure the resolution of the camera manually, but on the BeagleBone, we had to configure that just to get it to run.
It looks like there are still some configuration settings that we're not setting.
The text was updated successfully, but these errors were encountered: