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

No setCameraPose method on AprilTagProcessor #1433

Open
Goose66 opened this issue Feb 1, 2025 · 0 comments
Open

No setCameraPose method on AprilTagProcessor #1433

Goose66 opened this issue Feb 1, 2025 · 0 comments

Comments

@Goose66
Copy link

Goose66 commented Feb 1, 2025

This is an issue for future years/releasees of the SDK. There is no setCameraPose method for AprilTagProcessor objects. The setCameraPose method is only available on the builder. This means (AFAIK) that the only way to have multiple cameras in different positions on the robot is to have multiple AprilTagProcessors - one for each camera position. This also means you are enabling and disabling AprilTagProcessors when you switch cameras, which causes delays in the processor settling and providing AprilTag detections.

Since the setCameraPose only changes the parameters for calculating field position from the AprilTag pose, why not put the setCameraPose method on the AprilTagProcessor instead of the builder? That way you could have one AprilTagProcessor and keep it running (active), and just call setCameraPose with the corresponding camera position and orientation parameters when you switch cameras.

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

No branches or pull requests

1 participant