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

question about sample details? #15

Closed
DIVE128 opened this issue Mar 10, 2022 · 2 comments
Closed

question about sample details? #15

DIVE128 opened this issue Mar 10, 2022 · 2 comments

Comments

@DIVE128
Copy link

DIVE128 commented Mar 10, 2022

Hello, thank you for your great work and generous contribution. There‘re two details in code: (1) in the script(train_dtu.sh), # make
sure num_depth* interval = 203.45. (2) in t&t datasets, the depths are reversed. What's the role of these two operations?

@QT-Zhu
Copy link
Owner

QT-Zhu commented Mar 10, 2022

It's confusing and complicated to explain indeed. DTU gives a fixed depth range for each view, so the most ideal way to deliver the dataset is to give the min depth as well as the max depth and let users to apply their own ways of depth division. However, the dataset (or to say, the preprocessed version) assumes a default D, so it gives the depth interval instead (2.5mm in the text). As a result, if we want to change the value of D, we need to leverage a new parameter to scale the interval to make sure the range of depth is still the same.

I suppose you are referring to the flag of inverse_depth. It is an advantage with recurrent regularization, and you can check the paper of R-MVSNet for details.

@DIVE128
Copy link
Author

DIVE128 commented Mar 10, 2022

Thank you a lot

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

No branches or pull requests

2 participants