Closed FlachyJoe closed 8 years ago
Looks great, thanks! I'd like to add it to my usage instructions, however in my opinion it needs few teaks. Why didn't you add the full OpenMVS pipeline, like texturing? And could you change the hard coded paths to get them from some ENV variables for example and if not set to warn the user?
With some small changes, I added the script to the sample repository and instruction on how to use it on the Usage wiki page. Thanks again, @FlachyJoe!
You're welcome.
Le 27/08/2016 à 17:29, cDc a écrit :
With some small changes, I added the script to the sample repository and instruction on how to use it on the Usage wiki page. Thanks again, @FlachyJoe https://github.com/FlachyJoe!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cdcseacave/openMVS/issues/115#issuecomment-242923591, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ5BuaqRjVgFwAQx1ydz77wu2QDfvvvpks5qkFfKgaJpZM4JuEyi.
Hi, I'm happy to share a Python pipeline to proceed a reconstruction with OpenMVG and OpenMVS. You can basically call
python MvgMvs_Pipeline.py input_dir ouput_dir
or set arguments for each step from the command line (no script editing needed). This script has been tested under linux and you may adjust binary paths at lines 50+.MvgMvs_Pipeline.py.txt