-
Notifications
You must be signed in to change notification settings - Fork 34
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
Please document that Detecting two Apriltags with same id yields "undefined behavior" #218
Comments
Hi there - Tracking multiple tags with the same ID is not something that is currently supported in the SDK. What I would expect to happen with the current implementation is that the What you could perhaps do is make some kind of "tracking" algorithm based on the screen coordinates from the prior frame, to track which tag is which from frame to frame. Hope this helps! |
@aliyoob thank you for your question. This issue doesn't appear to be a documentation issue, which is what this ftcdocs github repository is designed to serve, but instead it appears to be a functionality issue. @Windwoes is correct, your specific use-case is undefined in the current system architecture. which might be a fun tiny game hint. If you have additional questions about the functionality of the AprilTag API, please post them to the FtcRobotController Discussions area. If there are issues that we need to address in documenting the AprilTag or VisionPortal APIs, we can create issues here in this repository. Good luck this season! |
Sorry, we'll keep this issue open for the documentation issue, but if you have additional functionality questions please be sure to ask away in the FtcRobotController Discussions area or on the FTC-Community technical forums. |
This would be a good Tech Tip though. |
Hi
I want to detect two Apriltag with same id
But there is a problem, the program can't distinguish the two tags. The numbers constantly keep changing and replacing each other. For example Yaw or distance are constantly keep changing between 6 to 14
The text was updated successfully, but these errors were encountered: