-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markers not detected #20
Comments
I think the one in the middle should work if the frame was a rectangle. On this image it looks more like a puzzle piece. Could you also attach the original image please? As for the markers on the side, I'm not sure if this is not too much distortion... Have you tried tweaking the parameters for your system using rqt_reconfigure? |
Have you modified file single.launch and included the right marker ID and its proper size? |
I would first try to detect another marker, just to make sure that AruCo does not have any problem with this specific marker. |
Good idea. Give a shot to the same scene with this marker (this is the most balanced one): As a sidenote: this coming weekend I intend to make a ROS Kinetic package of |
Is there a solution yet for the problem that markers are not recognized from a further than a specific distance? I ran a simulation, and when the camera is further away than 1m from a 6.5cm tag, it hasn't got any chance to detect it. Other libraries like apriltag has no problem at all with more than double the distance! |
I switched from ar track alvar to aruco due to some issues with camera model and the matrix used to compute the marker pose but I am now having problems getting aruco to detect the markers. Here is one example of the thresholded image using default parameters:
Why is this marker not being detected??
The text was updated successfully, but these errors were encountered: