Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Output depth data format #8

Open
arvkr opened this issue Jul 19, 2019 · 5 comments
Open

Output depth data format #8

arvkr opened this issue Jul 19, 2019 · 5 comments

Comments

@arvkr
Copy link

arvkr commented Jul 19, 2019

Hi,
Thanks for sharing the inference code. When the model infers the depth for the code from a single image, is the estimated depth in meters? What format is it exactly? Since the ground truth info is not there, I am not able to figure this out directly. Thank you.

@fcole
Copy link
Contributor

fcole commented Aug 7, 2019

The model estimates depth up to an unknown scale parameter, so the units themselves are not that meaningful. The error metrics we use for evaluation measure the accuracy of the depth map up to scale. This is a consequence of the training data (multi-view stereo) also having a scale ambiguity.

@astro-fits
Copy link

Hi fcole,
Do you mean that a depth map predicted by the pre-trained model is scaled by an unknown factor, in comparison with the "depth ground truth " ?

@jasjuang
Copy link

Hi, is the depth image predicted by the network a 32-bit continous floating-point image? Or is it just an 8-bit image?

@fcole
Copy link
Contributor

fcole commented Oct 26, 2019

Yes, the output is a floating-point value. Each output map is scaled by an unknown factor relative to the ground truth (i.e., it's not in units of meters or anything like that).

@astro-fits
Copy link

astro-fits commented Nov 7, 2019

Thanks for your reply. I found that such scaling factor is correlated with the normalization of depth ground truth (i.e. normalized from 1 to 3 or from 1 to 10 meters) when I train a model. The factor is also increased with the enhancement of training epoch.

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

No branches or pull requests

4 participants