Ask Your Question

Amy's profile - activity

2013-08-21 09:28:29 -0500 received badge  Nice Question (source)
2013-05-31 19:38:19 -0500 received badge  Necromancer (source)
2013-01-08 10:37:34 -0500 received badge  Student (source)
2012-12-05 04:58:50 -0500 received badge  Supporter (source)
2012-12-04 10:00:04 -0500 answered a question what is the best matching method for freak?

It is slow because SSSE3 is not enabled in OpenCV. I believe this is an issue. See my question. I'd be interested to know if you've found how to work it out since the time you posted here.

2012-12-04 09:57:18 -0500 answered a question How to use SSSE3?

I've been able to use SSSE3 but i had to dig into core OpenCV code. I used the author's code. I don't have any better approach as yet. In fact i also have a question on the subject here.

2012-12-04 09:52:17 -0500 asked a question How can i use a custom norm with BruteForceMatcher ?

I was trying to use FREAKS ( & BRISK ( author's code. They both define custom Hamming norms to use SSSE3 instructions.

Only there's a major difference between 2.3.x and 2.4.x in BruteForceMatcher. Since commit 957e80ab, BruteForceMatcher takes an (int normType) instead of a Distance.

Thus their code using custom norms is now broken, and I don't quite see how to use a custom distance without modifying library code.

The only solution i have seen up to now is

  1. add a <custom_norm_type> to the enum list in core.hpp (l.124)
  2. add calls to the custom norm function in similar ways than where NORM_HAMMING is used, i.e. lots of changes in core/src/stat.cpp

Now i have to recompile OpenCV & use a custom version. This is annoying.

If you check the links above, you'll see how much more practical it was before.

So what do you recommend now?