Avoid clearing HaarEvaluator::tofs variable (introduced fb8478eb7b
) in HaarEvaluator::setImage(...) since it won't be recomputed by HaarEvaluator::computeOptFeatures() for cases where the input image dimensions and requested search scales are the same as the previous. If none of the above change then it should be correct, and if they do change it will be computed correctly inside HaarEvaluator::computeOptFeatures() (in commit 952f9dbe62
)
I'm guessing there is a unit test for this that needs to be called 2x with the same image and search parameters (or another image with the same size) to illustrate the problem.pull/4017/head
parent
4743184078
commit
cab0ecdf19
1 changed files with 0 additions and 1 deletions
Loading…
Reference in new issue