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

match_clouds service from matcher_service node usage for 2D #79

Open
artemiialessandrini opened this issue Dec 14, 2019 · 0 comments
Open

Comments

@artemiialessandrini
Copy link

I'm not clear what this service could be used for, but based on wiki description:

This service takes two sensor_msgs/PointCloud2 messages as inputs (the first is the reference and the second the reading) and provides a geometry_msgs/Transform message as output.

I'm trying to accomplish an extrinsic calibration for two 2D Laser Scanners, which are perpendicularly mounted on AGV.

Since two Lidars are having intersection areas, thus it could be used for ICP based calibration,
My current idea is the following:

  1. Getting rid of unnecessary laser scan data areas, leaving only intersections;
  2. Decrease Lidars range to relatively small(4-5 m ), to collect a better data;
  3. Transform LaserScan into PointCloud2 type;
  4. Input initial_guess from current tf transform, thanks to Providing Initial Guess to matcher_service node #16;

So, now I have two PointCloud2 clouds: front (orange) and rear (blue).
Would this service be helpful? I'm open for any tips, suggestions regarding automatic calibration tool.

Screenshot from 2019-12-14 15-03-28

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