-
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
No difference after On-Chip Self-Calibration #6102
Comments
Can you share what the scene looks like as well? |
It does look noisier than I would expect. Since you tried self-calibration using the approach recommended in the white paper, I would be inclined to say that 1. Either the camera calibration has gone completely off or 2. Or the scene is a problem. In order to determine whether the unit is bad I would recommend pointing at a flat textured target (wall or carpeted floor). Measure the RMS noise with the Image Quality Tool sample app and check whether it is in the range expected for this camera by looking at the white paper describing the expected noise. Alternatively report back with your distance from target and I can tell you what noise you should expect. In either case pointing at a textured flat wall or white wall with projector and looking at depth map and noise should give clear indication of whether unit is simply bad. Finally, do you have any other RealSense cameras you can use? Do they all show same bad behavior? |
Thanks agrunnet for the reply. Yes it a conveyor belt with fast moving objects. I tried the self-calibration on another D415 but didn't get the results. The distance to the empty conveyor belt is 1044mm. |
At 1044mm we would expect a depth rms noise of 1.6mm assuming static image and textured surface. This is with no post-processing, like spatial filter or temporal filter. The D435 is much better for that. But like you said you would need to be closer. If you are 30cm for example you would have 90FOV at RMS of about 0.4mm-0.8mm. More importantly you can actually run at 90fps and even at 300fps with reduced vertical window size 848x100 in new FW which is being released soon. |
Thanks for the reply. It makes sense. The images that I posted on the top, are taken when the conveyor belt was stopped. I don't expect so much difference with this on-chip self-calibration but at least a minor improvement but I didn't see any difference. Also, I can not switch to D435. First of all, I have installed the camera and I can not change it. Second, based on the specs, D415 has a higher pixel density, which I believe it’s more accurate for any given area. D415 is more than 2x more accurate than the D435. So I want to stick to D415 camera. What can be done to make this self-calibration working? |
Hi, Based on the info you provided, I suspect the issue is not with the calibration of the camera but more likely the conditions under which it's being used (or possibly some other aspect of the camera). A few comments & questions:
Let me know if you have any questions or issues with these suggestions and let us know if any of it helps. |
As was mentioned earlier, this is not likely a calibration issue. Thanks for trying the self-calibration. As mentioned in the paper, if you print out the target in the appendix and use that, then you cannot get better results than that. If the problem persists then it is not a calibration issue. This target is an example of a "textured" scene. Regarding some of your results on calibration, you have very little inherent texture in the scene so if you use with projector on you would need to use "white wall mode". Also, as mentioned in the white paper, a periodic pattern like a checker board is not recommended for this self-calibration. |
Hi @soheilsbc Do you need further help on this issue? |
I have an Intel Realsense D415 camera that I don't get a good height. Today I tried On-Chip Self-Calibration on my camera. After the calibration, I have not noticed much difference. On the website, it shows a huge improvement but I have not noticed any. Any suggestion?
You may see the images before and after this Self-Calibration below:
Before:
After:
The text was updated successfully, but these errors were encountered: