-
Notifications
You must be signed in to change notification settings - Fork 99
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
RGBD Camera RGB data is clipped to 5 meters #12
Comments
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). Thanks, that's a good point. We'll look into it. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). |
Original comment by Stefan Kohlbrecher (Bitbucket: Stefan_Kohlbrecher). That's how |
Original comment by Neil Johnson (Bitbucket: realdealneil1980). To get around this issue in the meantime, while a bugfix is being explored, we have determined that we can set a few parameters on the RGBD camera to make it behave better, however we need to know what will be allowed during the actual qualification and contest runs. There are two main settings that affect the behavior of the sensor: |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
The latest code based on Ignition should have this issue fixed. Please reopen if there are still problems. |
Original comment by Alfredo Bencomo (Bitbucket: bencomo).
|
Original report (archived issue) by Neil Johnson (Bitbucket: realdealneil1980).
In our early testing of the RGBD sensor, we noticed that the output of BOTH the depth data and the RGB data is clipped to 5 meters. This appears to be a bug to me. A real RGBD sensor might not get good depth readings beyond 5 meters (we may challenge this limit in the future as well, but not now), but the RGB sensor is just a camera, and it should report data beyond the 5 meter distance.
The text was updated successfully, but these errors were encountered: