sfalexrog 91f6f6dd32 aruco_map: Use two-pass solvePnP ...

There are cases when iterative solvePnP method converges on a "wrong" camera position due to projectPoints not treating negative Z values properly.
Other methods don't seem to be affected by that, but their results differ from the iterative method slightly. By combining these two methods we
"nudge" the iterative method towards the correct camera position and get satisfactory results most of the time.

Sometimes, though, even with the "nudge" the iterative method diverges catastrophically, and this is not caught by the solver. We work around that
by assuming our camera position cannot be too far from the markers.

2019-05-20 12:29:42 +03:00

..

aruco_detect.cpp

aruco_pose: add param auto_flip

2019-03-21 20:55:35 +03:00

aruco_map.cpp

aruco_map: Use two-pass solvePnP

2019-05-20 12:29:42 +03:00

draw.cpp

aruco_pose: Try to draw as much of axes as possible

2019-04-07 22:46:38 +03:00

draw.h

aruco_pose: little style fix

2019-03-21 20:58:44 +03:00

genmap.py

genmap.py: remove unused arguments

2019-03-15 19:56:34 +03:00

utils.h

aruco_pose: fix snapping alrogithm

2019-03-21 20:55:35 +03:00