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

Proper documentation? #830

Closed
MaXL130 opened this issue Mar 24, 2017 · 7 comments
Closed

Proper documentation? #830

MaXL130 opened this issue Mar 24, 2017 · 7 comments
Labels

Comments

@MaXL130
Copy link

MaXL130 commented Mar 24, 2017

Hello everyone,
I'm trying to start using openMVG and I managed to set it up correctly. Right now I'm facing the issue, that I am not really sure how to use the library.

Is there any more documentation than the provided "Read the Docs"-Page and the comments in the source code, that I can use and have missed in the past?

Thanks for your help!

@rperrot
Copy link
Contributor

rperrot commented Mar 24, 2017

We know were lacking a more user friendly documentation with some tutorials, but we try to do our best to remedy to it. BTW, you could find some information at various places (from the high level to the low level view) :

  • use the proposed python pipelines (sequential/global located in your build software/sfm directory) to have a complete reconstruction tool (from images to view/structure) (maybe the best to start with openMVG) ;
  • consult the executables in software/sfm to see what you can do with the library (in a more step by step approach) ;
  • have a look at the samples (build it if they are not yet built), they illustrate some specific points of the library ;
  • have a look at the unit_tests, they often provide a (minimal) way to use internal structures/functions of openMVG.

If you don't find your specific information, please tell us what you want to do.

@MaXL130
Copy link
Author

MaXL130 commented Mar 24, 2017

Thanks for your answer! I will look into those. If I keep getting stuck, I will give you an update.

@pmoulon
Copy link
Member

pmoulon commented Mar 27, 2017

Feel free:

  • to close the issue when you have the answer to your question.
  • to share any reconstruction results (screenshot) ;-0

@MaXL130
Copy link
Author

MaXL130 commented Mar 27, 2017

I managed to get some results using the incremental, premade python pipeline and PMVS (see below).

As you can see, only one "half" of the cup was correctly reconstructed, with some minor holes in it. What am I doing wrong? I shot many pictures of the cup, going all around it multiple times in different heights.

clowncuphalf02
clowncup01

Edit: Pictures of the original cup (of course just two of them ;) )

img_9040
img_9039

@pmoulon
Copy link
Member

pmoulon commented Mar 27, 2017

Thank for the sharing.

The reconstruction is not complete since the image connection graph must be cut somewhere (certainly less feature for some part of the models).
You can have a look at the logged graph in the matching directory -> svg files (if you have graphviz installed they are exported).

You can try to make the graph denser by using a preset on the feature detector by adding the option -p HIGH on the ComputeMatches binary (do it in a new output directory else old feature will be read).

Or do the same dataset by adding a journal paper below your mug in order to have more texture and so more reliable feature matches from view to view.

@MaXL130
Copy link
Author

MaXL130 commented Mar 27, 2017

Thanks for the quick answer! Let's see what I can come up with 👍

@MaXL130
Copy link
Author

MaXL130 commented Mar 29, 2017

I am facing some issues, but for now I am going to close this issue, since the actual question was already answered. I am going to reopen, if there is sth new to report.

@MaXL130 MaXL130 closed this as completed Mar 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants