Skip to content
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

Support ATFL subscribing #1629

Open
amquake opened this issue Dec 9, 2024 · 1 comment
Open

Support ATFL subscribing #1629

amquake opened this issue Dec 9, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@amquake
Copy link
Member

amquake commented Dec 9, 2024

Currently, if users want to use custom AprilTag Field Layouts they can upload them to the UI for on-coprocessor multitag estimation.

There is no way to determine robot-side what tag layout is being used by a camera, nor publish a layout for the camera to use. This would make working with custom tag layouts easier, and enable custom layouts in simulation without needing special handling.

@mcm001
Copy link
Contributor

mcm001 commented Dec 9, 2024

I'm scared of dealing with synchronizing state between a roborio and coprocessors when neither is guaranteed to be on and connected or even running compatible versions of things at any given time lol. That's most of why this feature exists in code but purportedly doesn't actually work. How can we work around this constraint?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants