|
From: | Georg Klein |
Subject: | Re: [libcvd-members] FAST corner detection--- RFC |
Date: | Mon, 11 Jun 2007 13:55:05 +0100 (BST) |
On Fri, 8 Jun 2007, Edward Rosten wrote:
After a comment from Georg a while back, I now believe that the "max threshold for which point is still a corner" is a better way of doing the corner score.Does anyone ever use FAST corners without nonmax? I think that nonmax suppression should be the default operation. Is there a good reason to provide non nonmax functions?
Yes, I do. I initialise my features on max locations, then run detection on all cornery regions.
We have about 1e6 FAST detector functions. Ethan has contributed faster_* which are the fastest versions and are exact. I now have non SSE versions which are also exact (not yet in CVS). I'm planning on merging these in to:fast_corner_detect_?
Sounds cool. In my experience the SSE detection has occasionally been a bit haphazard in the configure script - it'd be nice to have a way of knowing that you are in fact getting the SCREAMING SIMD version if you want it. Currently, the compile brekage if you don't accomplishes that.
[Prev in Thread] | Current Thread | [Next in Thread] |