Ask Your Question
2

How to ensure that extractor does not remove keypoints

asked 2016-05-24 10:51:43 -0600

MrX gravatar image

I'm working with a framework that relies on keeping the number of keypoints constant before and after descriptor extraction. So far I applied a detection mask such that keypoints are not detected if they are close (e.g. 30 pixel) to the border of the image. Unfortunately, the extractor still removes a few keypoints. For example, I detect keypoints with the SURF detector on several octaves (!) and then use the FREAK extractor. Everything works fine if the number of octaves of the SURF detector is set to 1.

Can I sort out these keypoints by considering their size and octave? I removed all the keypoints with a size larger than 60 pixels but I've got still the same problem.

edit retag flag offensive close merge delete

Comments

In the last paragraph: what does it change in your case between removing manually the keypoints before extracting the descriptors and let the compute method do it automatically ?

Eduardo gravatar imageEduardo ( 2016-05-24 17:27:38 -0600 )edit

It's just that the framework I am working with uses the Eigen library to store keypoint and descriptor data. Furthermore, the detector and extractor class are implemented separately so I pass data from the detector to the extractor with Eigen. Unfortunately, it is quite painful to remove data from Eigen vectors and matrices. That's my problem.

MrX gravatar imageMrX ( 2016-05-25 03:52:11 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-05-27 02:31:22 -0600

MrX gravatar image

I checked the source code of the FREAK descriptor and it seems that it I would have to copy the values that are used there. I don't like this solution and decided to rewrite the framework with which I am working.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2016-05-24 10:51:43 -0600

Seen: 443 times

Last updated: May 27 '16