CascadeClassifier Stage Threshold Precision (Bug #1071)

Added by Frankie Fong almost 14 years ago. Updated almost 14 years ago.

Status:Done Start date:
Priority:High Due date:
Assignee:Vadim Pisarevsky % Done:

0%
Category:objdetect
Target version:-
Affected version: Operating System:
Difficulty: HW Platform:
Pull request:

Description

I tracked down a problem where the CascadeClassifier giving some false-negatives. The test set is the same as the training set used for traincascade. I expect the results would be identical.

The issue is the stage 'sum'-thresholding. Traincascade uses CV_THRESHOLD_EPS to limit the precision (?). And predictOrderedStump() from cascadedetect.cpp does not.

Attached is a patch where I added a static constant Stage::THRESHOLD_EPS and used it inside predictOrderedStump(). This could possible be extends to other predictXXX() functions. But I don't have the sample set to verify.

cascadedetect_r89.diff (1.4 kB) Frankie Fong, 2011-05-17 08:36 am

Associated revisions

Revision 51c68423
Added by Vadim Pisarevsky almost 14 years ago

alter the read stage.threshold to match traincascade behavior (ticket #1071)

History

#1
Updated by Frankie Fong almost 14 years ago

specifying openCV version 2.2

#2
Updated by Vadim Pisarevsky almost 14 years ago

thanks! stage.threshold has been altered to match traincascade values in SVN trunk r5146.

  • Status changed from Open to Done
  • (deleted custom field) set to fixed

Also available in: Atom PDF