Extract Camera class - #143
Merged
Merged
Conversation
cuttestkittensrule
approved these changes
Feb 15, 2026
cuttestkittensrule
left a comment
Collaborator
There was a problem hiding this comment.
Looks good! There are some small things that can be better, but overall it is ready do go.
…ier' to the Camera constructor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This simplifies
MultiPhotonPoseEstimator.Builder. It also allows users to create constant fields for each camera (or different cameras for different drivetrains).The
Camerais passed to the callback that the user provides toprocessAllUnreadResults(). TheCameraclass can be subclassed, to allow teams to add additional data about the camera (for instance, you could provide a multiplier to apply to the standard deviation so that you could give a higher weight to some cameras).