-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Comments
Hello @UweDorsch, You may find this discussion on the RealSense Community helpful. Regards, |
Hello Jesus, kind regards |
[Realsense Customer Engineering Team Comment] 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, |
How to access the document. Its behind a login wall. Thanks! |
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, |
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)
The text was updated successfully, but these errors were encountered: