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

Quality of masured depth data #1235

Closed
UweDorsch opened this issue Feb 26, 2018 · 5 comments
Closed

Quality of masured depth data #1235

UweDorsch opened this issue Feb 26, 2018 · 5 comments
Assignees

Comments

@UweDorsch
Copy link

Required Info
Camera Model Intel RealSense 435
Firmware Version 05.08.15.00
Operating System & Version Win 10 Pro 64
Platform PC
SDK Version 2.10.0

Quality of masured depth data

During my first tests with the D435 Camera I observed that the measured depth points always building smooth surfaces. There is no noise in the depth data if you look at a smal selection of points. But you can see that there are structures like little waves in the depth data. It looks like some preprocessing to denoise the data, but this effect looks like there is a structure in a flat surface. It would be helpfull to get the raw data with all the noise and then I can look what points I would use or not.

I tried to use different presets, the high accuracy delivers the best results (smalest waves), but I did not find anything to get depth data like I get from Kinect or Primsense.
I think that post processing the output is not the solution, I just like to get a less preprocessed set of depth data. The problem is getting worse with further distance (>1,5m).
I would be happy to get some hints.

There is an issue with a similar problem especial for smal distances:
Finding the best acquisition parameters (D415) (#1171)

@jlgarcia75
Copy link

Hello @UweDorsch,

You may find this discussion on the RealSense Community helpful.

Regards,
Jesus G.
Intel Customer Support

@jlgarcia75 jlgarcia75 self-assigned this Feb 26, 2018
@jlgarcia75 jlgarcia75 added the Waiting for Customer Waiting for customer response. label Feb 26, 2018
@UweDorsch
Copy link
Author

Hello Jesus,
thank you for your response.
The discussion on the RealSense Community is exactly about my problem. But it is a little bit disappointing, because it looks like there is no way to get depth data from the RealSense Camera with comparable quality to the kinect depht data.
The wavy depth values sems to be the result of the internal depth processing inside the RealSense Camera. Is there a opportunity to get less preprocessed data?

kind regards
Uwe

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hello @UweDorsch,

Have you seen the RealSense Tuning whitepaper? https://realsense.intel.com/wp-content/uploads/sites/63/BKMs-For-Tuning-RealSense_D4xx_Cameras_WP_1.7.pdf

Regards,
Jesus G.
Intel Customer Support

@farrukh-x2
Copy link

How to access the document. Its behind a login wall. Thanks!

@jlgarcia75
Copy link

Hello @ruktech,

You can find the tuning document here:https://www.intel.com/content/www/us/en/support/articles/000027833/emerging-technologies/intel-realsense-technology.html.

Regards,
Jesus
Intel Customer Support

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

No branches or pull requests

5 participants