Floating point vs binary features matching scores about dbow3 HOT 6 OPEN

I also encountered the same problem. After I read the source code, I found that maybe there is something wrong with Vocabulary.cpp. In the function void Vocabulary::transform(const cv::Mat &feature, WordId &word_id, WordValue &weight ) const only considered the binary descriptors.

you could fix the bugs by yourself or use DBoW2 instead:)

from dbow3.

Same Problem

from dbow3.

I also encounter this problem. see the source code find the problem.

from dbow3.

I met with the same problem using SIFT and SURF and finally sovled. Always no query results even there is a same image in the database. While I found that the distance is always inf after debugging step by step. I output the input variables in function "DescManip::distance(feature, m_nodes[id].descriptor)",then I checked both feature extraction method, they are not the same...This is the core problem for me.

from dbow3.

I'm going to take a look at the problem and try to reproduce it, and solve it. Thanks for the info and sorry for the delay. I was busy with it. If somebody could post a patch with the solution it would be great! In any case, I moved long time ago to fbow. I strongly recommend using it. Why do you prefer DBOW3?

from dbow3.

Has anyone found a solution to this issue? I'm using DBOW2 with SURF, but having issues there as well and I'd much rather have out-of-the-box support for SURF.

from dbow3.