Skip to content

Commit d6c222b

Browse files
author
AleksandrPanov
committed
update aruco_faq
1 parent 1b85f01 commit d6c222b

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

modules/aruco/tutorials/aruco_faq/aruco_faq.markdown

+14
Original file line numberDiff line numberDiff line change
@@ -149,3 +149,17 @@ You can cite the original ArUco library:
149149
> S. Garrido-Jurado, R. Muñoz-Salinas, F. J. Madrid-Cuevas, and M. J. Marín-Jiménez. 2014.
150150
> "Automatic generation and detection of highly reliable fiducial markers under occlusion".
151151
> Pattern Recogn. 47, 6 (June 2014), 2280-2292. DOI=10.1016/j.patcog.2014.01.005
152+
153+
Problems and solutions
154+
------
155+
156+
- Incorrect ARUCO detection with bigger markers in high resolution images.
157+
- Try increasing adaptiveThreshWinSizeMin, adaptiveThreshWinSizeMax and/or decreasing adaptiveThreshConstant.
158+
- Try reducing the image resolution to VGA.
159+
- See issue https://github.com/opencv/opencv_contrib/issues/2811
160+
- Incorrect estimation of the pose of a single markers.
161+
- It is important to remark that the estimation of the pose using only 4 coplanar points is subject to ambiguity. In general, the ambiguity can be solved, if the camera is near to the marker. However, as the marker becomes small, the errors in the corner estimation grows and ambiguity comes as a problem.
162+
- Try increasing the size of the marker you're using, and you can also try non-symmetrical (aruco_dict_utils.cpp) markers to avoid collisions.
163+
- Use multiple markers (ArUco/ChArUco/Diamonds boards) and pose estimation with estimatePoseBoard(), estimatePoseCharucoBoard()
164+
- Use solvePnP() with the SOLVEPNP_IPPE_SQUARE option.
165+
- See issue https://github.com/opencv/opencv/issues/8813

0 commit comments

Comments
 (0)