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

NaN/Inf handling in head registration #9

Open
pgrice opened this issue May 15, 2014 · 2 comments
Open

NaN/Inf handling in head registration #9

pgrice opened this issue May 15, 2014 · 2 comments
Assignees
Labels

Comments

@pgrice
Copy link
Member

pgrice commented May 15, 2014

Occasionally the Pixel23d callback or head registration callback will die due to the presence of "Invalid (NaN, Inf) point coordinates given to radiusSearch!"

@pgrice pgrice added the bug label May 15, 2014
@pgrice pgrice self-assigned this May 15, 2014
@pgrice pgrice changed the title NaN/Inf handling in pixel_23d and Head registration NaN/Inf handling in head registration May 15, 2014
@pgrice
Copy link
Member Author

pgrice commented May 15, 2014

After further investigation, I cannot actually get this to happen with the looking-to-point callback (using Pixel23d), but it appears to occur on the edges of the image for Head Registration. I seem to remember the depth image not covering the whole RGB image, such that in some spots, good depth information is not available for the RGB image, and this is possibly what is causing this issue.

@pgrice
Copy link
Member Author

pgrice commented May 16, 2014

The issue occurs throughout the image, not only in the margins or in areas without good associated pointcloud data. The issue occurs even when the kinect is launched in the standard mode. Recent developments, then, seem to have produced this bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant