The right parameters setting to test feature detectors

asked 2014-04-29 01:27:09 -0500

jpl gravatar image

updated 2014-04-29 01:34:14 -0500

berak gravatar image

Results of the evaluation of feature detectors depend on the values we give to their parameters, like the threshold , the number of octaves... How can I know which values are best? Some articles say that they use the values that the detectors' authors have used to evaluate them, but what are these values for the FAST, SURF and BRISK?

edit retag flag offensive close merge delete



Simply said, you need a ground truth set and a test set of your matches outcome. There are several ways to define optimal parameters for a feature detecture, like using ROC curves, precision-recall curves. I think you need to go dig deeper into evaluation frameworks of machine learning techniques.

StevenPuttemans gravatar imageStevenPuttemans ( 2014-04-29 04:11:19 -0500 )edit

Simple google gave me this very interesting publication on the topic!

StevenPuttemans gravatar imageStevenPuttemans ( 2014-04-29 04:12:31 -0500 )edit

Thanks StevenPuttermans for your answer. Speaking of ground truth set, I found this term all lot in articles, what does it mean exactly?

jpl gravatar imagejpl ( 2014-04-29 07:04:12 -0500 )edit

for example if you are detecting an object using feature descriptors, you assign a ground truth (location) to the object in the image. When performing your detection then, you can check if the found detection is actually a truthfull one. Ground truth means what is really there, and it has to be compared to the output of any algorithm.

StevenPuttemans gravatar imageStevenPuttemans ( 2014-04-29 07:49:44 -0500 )edit