different paddings in cvtColorTwoPlane() for biplane YUV420
* Different paddings support in cvtColorTwoPlane() for biplane YUV420
* Build fix for dispatch case.
* Resoted old behaviour for y.step==uv.step to exclude perf regressions.
Co-authored-by: amir.tulegenov <amir.tulegenov@xperience.ai>
Co-authored-by: Alexander Smorkalov <alexander.smorkalov@xperience.ai>
* 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>
Return accumulator value in HoughLines algorithm
* try to solve #17050
use cv_wrap_as
add python test
parameters
* review
* move wrapper to imgproc/bindings.hpp
Bit-exact Nearest Neighbor Resizing
* bit exact resizeNN
* change the value of method enum
* add bitexact-nn to ResizeExactTest
* test to compare with non-exact version
* add perf for bit-exact resizenn
* use cvFloor-equivalent
* 1/3 scaling is not stable for floating calculation
* stricter test
* bugfix: broken data in case of 6 or 12bytes elements
* bugfix: broken data in default pix_size
* stricter threshold
* use raw() for floor
* use double instead of int
* follow code reviews
* fewer cases in perf test
* center pixel convention
Alexander Alekhin