-
Notifications
You must be signed in to change notification settings - Fork 12
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
Depth Image zero when to close #1159
Comments
That seems to me like a problem in the segmentation and object fitting algorithms. These algorithms do not detect the circumstances in which they perform well, which can lead to errors. |
The cause is just that we don't get the data from the sensor that we would like to have. There is just no depth known for these pixels. So there just isn't any data. |
That is just the way the camera works, isnt it? Not really anything we can do about it. Only thing we can do is use the data we do have |
The question is Does the robot work the same as the simulator. In that case we need to make sure that we are never to close. |
In that case we should be aware that our algorithms dont work when we are too close. Not "never be too close" because I can see that coming back to bite us |
For I now I only experienced it in simulation
Depths that are too close or too far away are zero.
This gives problems in segmentation and object fitting when HERO is too close to the object.
The text was updated successfully, but these errors were encountered: