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

HammingSeg apparently not being used #4

Open
protobits opened this issue May 6, 2015 · 0 comments
Open

HammingSeg apparently not being used #4

protobits opened this issue May 6, 2015 · 0 comments

Comments

@protobits
Copy link

Hi,
I'm using latest stable OpenCV (not v3) and trying out FREAK. I would like to use the special matching that is used in the demo. I was previously using the BF matcher in the following way:

matcher = boost::make_sharedcv::BFMatcher(cv::NORM_HAMMING);

Later, I add descriptors using add(). Finally, I match using knnMatch().

To try your custom matcher I replaced the first line with:

matcher = boost::make_sharedcv::BruteForceMatcher<cv::HammingSeg<30,4>>();

However, it does not seem to be working. I don't think the HammingSeg operator() is even being called. I tried printing something to the screen from there and it does not seem to be reaching the code.

Do you know if this should work like this?

By the way, when using this custom matcher, the idea is not to require the standard ratio-based test between 1st and 2nd neighbors, right?

EDIT: I checked the demo, and placed the print line on the operator() function and it does not seem to be using this either. I'm suspecting it uses standard HAMMING based BFMatcher.

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

1 participant