-
Notifications
You must be signed in to change notification settings - Fork 25
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
So the generated pfm files were not actually used in this pipeline? #6
Comments
Yes, you are right. The existing codes are just OpenMVS as I said in the README. I have not released the code for transforming the generated pfm files to the format of dmp. You can refer to https://github.com/cdcseacave/openMVS/blob/master/libs/MVS/Interface.h#L631 |
Have you solved this problem? |
The code for converting the output of MVSNet to the DMap format of OpenMVS has been open-sourced :https://github.com/chaytonmin/DeepMVS/blob/master/depth2dmap.py |
It seems that DensifyPointCloud.exe does not have an option to choose a local dmap, and it recalculates the dmap every time it runs. Is there any solution to this? |
I've tested the code and managed to generate multiple pfm files. However, after running openmvs, I realized that these generated pfm files were not adopted at all. The final results still depend on the estimated dmp files by openmvs's DensifyPointCloud.exe, so the generated result have nothing to do with the pfm files?
Please confirm this. Thanks!
The text was updated successfully, but these errors were encountered: