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

GPU octree error with big PointClouds. #2008

Closed
tensorfreitas opened this issue Sep 26, 2017 · 5 comments
Closed

GPU octree error with big PointClouds. #2008

tensorfreitas opened this issue Sep 26, 2017 · 5 comments
Labels
needs: code review Specify why not closed/merged yet

Comments

@tensorfreitas
Copy link

tensorfreitas commented Sep 26, 2017

⚠️ This is a issue tracker, please use our mailing list for questions: www.pcl-users.org. ⚠️

Your Environment

  • Operating System and version: Windows 10 Pro / Ubuntu 16.04
  • Compiler:
  • PCL Version: 1.8.1

Expected Behavior

pcl::gpu::Octree should be able to build for different PointClouds.

Current Behavior

It works on some PointClouds but in other gives the following error: Error: unspecified launch failure D:/Libraries/pcl-pcl-1.8.1/gpu/octree/src/cuda/octree_builder.cu:403

Possible Solution

Code to Reproduce

pcl::PointCloud<pcl::PointXYZ>::Ptr cloud(new pcl::PointCloud<pcl::PointXYZ>);
pcl::io::loadPCDFile("Original.pcd", *cloud);
pcl::gpu::Octree::PointCloud cloud_device;
cloud_device.upload(cloud->points);`
pcl::gpu::Octree octree_device;
octree_device.setCloud(cloud_device);
octree_device.build();

Context

Althogh it fails with bigger pointClouds the test works with the provided tests of DataGenerator data;
data.data_size = 871000;

Has anyone faced this kind of problem?

@SergioRAgostinho
Copy link
Member

Is the pointcloud you're using, uploaded somewhere so we can give it a try?

@taketwo taketwo added the needs: author reply Specify why not closed/merged yet label Oct 19, 2017
@tensorfreitas
Copy link
Author

Original.txt

Here is the pointCloud. I put it in a txt file because the pcd file upload did not work in the issue. Thanks for the help!

@SergioRAgostinho SergioRAgostinho added needs: code review Specify why not closed/merged yet and removed needs: author reply Specify why not closed/merged yet labels Nov 23, 2017
@SergioRAgostinho
Copy link
Member

So I was not exactly able to reproduce your problem because I think it's something dependent on your hardware already. "Unspecified launch failure" happens normally when you try to launch kernel with incorrect grid/thread/warp sizes which your target hardware doesn't support. (Sorry for being imprecise with the lingo but I'm not experienced in CUDA)

I do get however a faulty memory access the moment I used 951 points of the cloud you provided, being caused by octree_builder.cu:246. Whatever the fix is for my problem, I'm almost certainly sure it won't solve yours.

On which hardware are you trying to run this? And what is your CUDA runtime version?

@SergioRAgostinho SergioRAgostinho added needs: author reply Specify why not closed/merged yet and removed needs: code review Specify why not closed/merged yet labels Nov 26, 2017
@frozar frozar mentioned this issue Dec 1, 2017
@tensorfreitas
Copy link
Author

Sorry for the late response, I have been using a GTXM960 with cuda 8.0. even with the Kernel with grid and block size of 1 it fails with the first 960 points (which does not happen in CPU version). I think the problem is in the algorithm. I spent some days on this, but was not able to figure out why it occurs.

I think it might be due to the fact there are some outliers in those points and the algorithm gives an error in that case. Because if I run without those outliers, the algorithm runs smoothly. Sorry for not spotting exactly were the problem occured, but since it was for a work project, I had to move on with other tasks.

@SergioRAgostinho SergioRAgostinho added needs: code review Specify why not closed/merged yet and removed needs: author reply Specify why not closed/merged yet labels Dec 20, 2017
@SergioRAgostinho
Copy link
Member

Hopefully closed with the merge of #3627

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: code review Specify why not closed/merged yet
Projects
None yet
Development

No branches or pull requests

3 participants