-
Notifications
You must be signed in to change notification settings - Fork 21
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
What is the use of 1.312 on line 47 in DistDepth/utils.py? #27
Comments
The term is associated with 13.12cm stereo baseline used to render SimSIN Dataset of the during training. The unit of stereo_baseline used for training is 10cm ( DistDepth/datasets/SimSINbase.py Line 187 in 45e7e3f
|
Thank you very much for your reply! Can I understand that the formula Depth= Baseline*focal/disparity is applied to this part of the code? Baseline corresponds to 1.312, is scaled_out equivalent to disparity/focal? Is the output of the network actually a disparity? For example, here, normalizing to [0,10] is equivalent to doing focal length transformation? In supervised training, what will be the result if normalization is not performed here?
|
One view is as you said the scaled_out is focal/disparity under 10cm baseline. So just scale up with wider baseline. Another view: it is a ratio problem. Suppose a network learns depth from intrinsic/ extrinsic projection in the definition of baseline 10cm (and since it is self-supervised no groudtruth are provided to correct the scale), but actually it is 13.12cm. From the equation depth = baseline*focal/disparity the same image with the same focal and disparity, the depth is proportional to baseline, and thus the actual depth is *1.312 Normalizing to [0, 10] gives a range prior of depth in views, which can actually cause a bit scale not matching to test scene, as the same issue of MonoDepth works. In supervised learning, you will have all metric stuff and doesn't need scaling. Even learned in inverse depth, you also have metric inverse depth. |
What is the use of 1.312 on line 47 in DistDepth/utils.py? Why is the scale factor here calculated like this? Without using stereo matching? Can you explain the principle? Thanks!
The text was updated successfully, but these errors were encountered: