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

pcl segmentation error when estimate multiple tags #41

Open
huiwenzhang opened this issue Jul 5, 2017 · 7 comments
Open

pcl segmentation error when estimate multiple tags #41

huiwenzhang opened this issue Jul 5, 2017 · 7 comments

Comments

@huiwenzhang
Copy link

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:

<launch>
	<arg name="marker_size" default="5.8" />
	<arg name="max_new_marker_error" default="0.08" />
	<arg name="max_track_error" default="0.2" />

	<arg name="cam_image_topic" default="/camera/depth_registered/points" />
	<arg name="cam_info_topic" default="/camera/rgb/camera_info" />
	<arg name="output_frame" default="/camera_link" />

	<node name="ar_track_alvar" pkg="ar_track_alvar" type="individualMarkers" respawn="false" output="screen">
		<param name="marker_size"           type="double" value="$(arg marker_size)" />
		<param name="max_new_marker_error"  type="double" value="$(arg max_new_marker_error)" />
		<param name="max_track_error"       type="double" value="$(arg max_track_error)" />
		<param name="output_frame"          type="string" value="$(arg output_frame)" />

		<remap from="camera_image"  to="$(arg cam_image_topic)" />
		<remap from="camera_info"   to="$(arg cam_info_topic)" />
	</node>

</launch>

However, once I showed the markers in front of the camera, it throws error as follows:

[pcl::SampleConsensusModel::getSamples] Can not select 0 unique points out of 0!
[pcl::RandomSampleConsensus::computeModel] No samples could be selected!

How can I fix that? @pirobot

@dwhit
Copy link

dwhit commented Jul 31, 2018

@huiwenzhang Did you ever solve this issue? I am having a similar problem.

@huiwenzhang
Copy link
Author

@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.

@Behery
Copy link

Behery commented Oct 19, 2018

Did this work with the Xtion camera? I'm currently also using a kinect camera and I'm having the same problem.

@XYudong
Copy link

XYudong commented Oct 8, 2019

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

@leo-murta95
Copy link

@XYudong did u solve it? i have same problem

@divishad12
Copy link

I am having the similar issue. Did anyone find the solution?

@tauzn-clock
Copy link

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

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

7 participants