-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Normals at edges all go trough origin #3269
Comments
Nice image. Let's try some cheap tricks first: can you try the fix in #3169 and see if it solves your problem? |
I tried the patch, but it makes no difference. But for me that makes sense, because the pointcloud is very close to the origin. |
I was hoping this issue might have been fixed in 1.9.1, but it both happens in 1.8.1 and 1.9.1 |
I wrote an mvce and would be glad if somebody could confirm this. It uses ros melodic, a realsense d415 and pcl 1.9.1:
CMakeLists.cmake
|
I tried it with the other normal estimation method from here and I don't get this strange artefacts, but it takes 30s so this is not really an option. |
So looking at the data, all the points that connect to the origin have nan values. If this new behavior of visualizing nans like this is normal, somebody can close this. Otherwise some advice would be appreciated. |
Hey. I see your mvce still requires ros, so it can be further reduced. Can you save your test pointcloud as a pcd file and upload it somewhere. Make your mvce load that pcd and render it as you're currently already doing. |
Ok, I got around to make the example smaller:
test.cpp
PCD file |
Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs. |
The issue is best illustrated in an image:
Your Environment
Context
I try to estimate the normals of some bricks lying on the floor. But as seen in the image all the normals at edges connect to the origin.
Expected Behavior
Proper normals estimation
Current Behavior
Code to Reproduce
I could upload a rosbag if needed.
Possible Solution
I have no clue, but I saw that the neighborhoud search radius makes the problem worse the bigger it is. The above image uses a radius of 15. The one below uses a radius of 5:
The text was updated successfully, but these errors were encountered: