-
Notifications
You must be signed in to change notification settings - Fork 130
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
pcl segmentation error when estimate multiple tags #41
Comments
@huiwenzhang Did you ever solve this issue? I am having a similar problem. |
@dwhit Hi, Sorry for late response. I think the problem is still there. I haven't touch the problem for a long time. Now I am using a Xtion camera with a robot. Maybe I will test the function recently. |
Did this work with the Xtion camera? I'm currently also using a kinect camera and I'm having the same problem. |
I am using Kinect having the same issue |
@XYudong did u solve it? i have same problem |
I am having the similar issue. Did anyone find the solution? |
This is not exactly a fix but you could use individualMarkersNoKinect with /camera/rgb/image_color. This method may be less accurate as we are using the camera pixel data rather than the lidar data. I suspect that this is only an issue if the tags used are too small. As the results, the point cloud is too distorted to be processed by pcl. Here is a similar issue I found in another thread. robofit/but_velodyne#32 |
Hi,
I want to use this package to estimate marker pose. I used a kinect to get depth and camera_info information, which are published on /camera/depth_registered/points and /camera/rgb/camera_info topic. I start the camera driver node, it works fine. and then I start the launch file with ' roslaunch ar_track_alvar pr2_indiv.launch`. The launch file was modified as follows:
However, once I showed the markers in front of the camera, it throws error as follows:
How can I fix that? @pirobot
The text was updated successfully, but these errors were encountered: