-
Notifications
You must be signed in to change notification settings - Fork 236
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
how and where "the number of neighbors (a parameter)" can be set when using PCL GPU #104
Comments
That part of the code is deprecated and should not be used. How large is your point cloud? |
Thanks for your reply. If I only send the 8000 points as sensor_msgs/PointCloud2 to GPD, it's fast to compute the surface normal, but the classification step takes about 15~20 seconds... |
Yesterday I tried to use PCL_GPU in GPD and CloudSamples as the input, the whole process is very fast, but sometimes it can't generate any valid grasp pose, sometimes it does. I only test it for one scene ( bottle on a table ) for a while, further test will be done. |
Yes, it should be off. When I find the time, I'll remove the GPU part of the code completely because it does not work reliably.
That's a very large point cloud. You could reduce its size and/or downsample it in order to reduce the number of points. |
Hi,
On my computer GPD takes about 15s to calculate the surface normal using PCL CPU, which is a bit long for my project. Therefore I want to use the GPU version. You mentioned that "unfortunately, the surface normals produced by the PCL GPU module can often be incorrect. The correctness of these normals depends on the number of neighbors (a parameter).". But I can't find where this parameter can be tuned.
Could you please show an example to set this parameter? Thanks!
The text was updated successfully, but these errors were encountered: