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

pass back corner detections #130

Open
inventor2525 opened this issue Jun 4, 2022 · 2 comments
Open

pass back corner detections #130

inventor2525 opened this issue Jun 4, 2022 · 2 comments

Comments

@inventor2525
Copy link

inventor2525 commented Jun 4, 2022

Just wondering if there's interest in this. Possibly made optional.

Reasons we wanted the change:

  1. To try removing rotational ambiguity in limited instances using extra points, possibly inner corners
  2. Track tag looking for blur resistant extra markers (possibly until ArucoDCF [not the current ros node]).
  3. Add other adjacent markers in the future (color calibration).
@christian-rauch
Copy link
Contributor

I guess publishing the corner coordinates too could be useful. I did this in the ROS2 version of the node: https://github.com/christianrauch/apriltag_ros. However, I recommend using standard messages for this instead of raw lists of concatenated coordinates.

So far, this would be useful for debugging and visualisation. I don't follow how you want to use them in the applications you listed. Most of them will require changes to the library itself, not this ROS node.

@julled
Copy link

julled commented Dec 27, 2022

I would also interested in receiving the corner and center detections as e.g. Detection2D messages

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

No branches or pull requests

4 participants