* goodFeaturesToTrack returns also corner value
(cherry picked from commit 4a8f06755cf93785a82a455a2035a2ff572cafae)
* Added response to GFTT Detector keypoints
(cherry picked from commit b88fb40c6ea037e5283e4fbcf0ffde160c65a035)
* Moved corner values to another optional variable to preserve backward compatibility
(cherry picked from commit 6137383d32859efad7b44dd8a798e7b69f68dec5)
* Removed corners valus from perf tests and better unit tests for corners values
(cherry picked from commit f3d0ef21a78b7d0dc8696c457a6fabecfbe5e8ff)
* Fixed detector gftt call
(cherry picked from commit be2975553ba01a7d2e63f549fadccec6d7d56797)
* Restored test_cornerEigenValsVecs
(cherry picked from commit ea3e11811faee63487449983c0b80ff8ee35bbac)
* scaling fixed;
mineigen calculation rolled back;
gftt function overload added (with quality parameter);
perf tests were added for the new api function;
external bindings were added for the function (with different alias);
fixed issues with composition of the output array of the new function (e.g. as requested in comments) ;
added sanity checks in the perf tests;
removed C API changes.
* minor change to GFTTDetector::detect
* substitute ts->printf with EXPECT_LE
* avoid re-allocations
Co-authored-by: Anas <anas.el.amraoui@live.com>
Co-authored-by: amir.tulegenov <amir.tulegenov@xperience.ai>
Added gradiantSize param into goodFeaturesToTrack API (#9618)
* Added gradiantSize param into goodFeaturesToTrack API
Removed hardcode value 3 in goodFeaturesToTrack API, and
added new param 'gradinatSize' in this API so that user can
pass any gradiant size as 3, 5 or 7.
Signed-off-by: Vipin Anand <anand.vipin@gmail.com>
Signed-off-by: Nilaykumar Patel<nilay.nilpat@gmail.com>
Signed-off-by: Prashanth Voora <prashanthx85@gmail.com>
* fixed compilation error for java test
Signed-off-by: Vipin Anand <anand.vipin@gmail.com>
* Modifying code for previous binary compatibility and fixing other warnings
fixed ABI break issue
resolved merged conflict
compilation error fix
Signed-off-by: Vipin Anand <anand.vipin@gmail.com>
Signed-off-by: Patel, Nilaykumar K <nilay.nilpat@gmail.com>
When using OCL, the results of goodFeaturesToTrack() vary slightly from
run to run. This appears to be because the order of the results from
the findCorners kernel depends on thread execution and the sorting
function that is used at the end to rank the features only enforces are
partial sort order.
This does not materially impact the quality of the results, but it
makes it hard to build regression tests and generally introduces noise
into the system that should be avoided.
An easy fix is to change the sort function to enforce a total sort on
the features, even in cases where the match quality is exactly the same
for two features.
