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 on-camera apriltag detections #46

Draft
wants to merge 14 commits into
base: feature/remote_head_support
Choose a base branch
from

Conversation

davidirobinson
Copy link
Contributor

@davidirobinson davidirobinson commented Jun 17, 2022

Stacked behind #44

  • Handle apriltag detection messages from the multisense camera and publish as custom ROS messages
  • Add dynamic reconfigure of apriltag parameters (parameters will be hidden if Source_AprilTag_Detections is not available on the camera)

@davidirobinson davidirobinson marked this pull request as ready for review June 22, 2022 00:07
carnegierobotics#42)

* Properly handle the full translation between left/aux rectified images

* Fix aux projection logic

* Add helper functions to prevent locking
Comment on lines +1 to +3
# Apriltag corner point in pixels
float64 x
float64 y
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a sensor_msg which has this data?

Comment on lines +1 to +28
# The family of the tag
string family

# The ID of the tag
uint32 id

# The hamming distance between the detection and the real code
uint8 hamming

# The quality/confidence of the binary decoding process
# average difference between intensity of data bit vs decision thresh.
# Higher is better. Only useful for small tags
float32 decisionMargin

# The 3x3 homography matrix (in row-major order) describing the projection
# from an "ideal" tag (with corners at (-1,1), (1,1), (1,-1), and (-1,-1))
# to pixels in the image
float64[9] tagToImageHomography

# The 2D position of the origin of the tag in the image
float64[2] center

# The 4 tag corner pixel locations in the order:
# point 0: [-squareLength / 2, squareLength / 2]
# point 1: [ squareLength / 2, squareLength / 2]
# point 2: [ squareLength / 2, -squareLength / 2]
# point 3: [-squareLength / 2, -squareLength / 2]
AprilTagCornerPoint[4] corners
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a standard AprilTag message we can use here? Haven't done really any digging

mattalvarado
mattalvarado previously approved these changes Jun 23, 2022
Copy link
Contributor

@mattalvarado mattalvarado left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I would make sure to sync with @QuentinTorg before landing since this will almost certainly conflict with his dynamic reconfigure work.

@davidirobinson davidirobinson changed the base branch from master to feature/remote_head_support June 29, 2022 17:54
@davidirobinson davidirobinson marked this pull request as draft June 30, 2022 17:03
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

Successfully merging this pull request may close these issues.

2 participants