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

Vocabulary sparsity problem #119

Open
joyousrabbit opened this issue Jun 19, 2016 · 2 comments
Open

Vocabulary sparsity problem #119

joyousrabbit opened this issue Jun 19, 2016 · 2 comments

Comments

@joyousrabbit
Copy link

joyousrabbit commented Jun 19, 2016

Hello everyone,

I'm thinking these days a problem and hope your help: Is the vocabulary too big for practice?

As you see, the vocabulary has 1 million items. However every frame, on average has only about 1000 feature points. I can't image any statistic sense by projecting from 1000 to 1 million. Most similar features will miss matching just cause of this huge sparsity (I didn't take experiment, just some feeling).

Besides, compare 2 vectors both of 1 million is not that fast.

So, my question is, why not keep the vocabulary little (about 1000 words)? Then even a brute force search on 10000 keyframes takes only 1000*10000 (just 10 times than comparing 2 vectors of 1 million).

Any idea is welcome. Thanks!

@rikpires
Copy link

rikpires commented Jun 20, 2016

DBoW2 method is not an exhaustive searching method. It's somehow like a k-d tree searching. The searching efficiency is pretty good. The searching part takes about only 5ms for average and less than 40ms for maximum in the author's experiment. The author provides a huge data base so that everyone can use the same data base instead of training his own for each scene. And of course, if you want to speed up or your case is special or simple, you might train your own database.

@joyousrabbit
Copy link
Author

@rikpires
Thank you for comment. What will happen if we keep, in DBoW2, only 1 level but with 1000 leaves?

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