Matthew Self 72672c293f Make goodFeaturesToTrack() return deterministic results ... 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.		2016-07-25 21:17:54 -07:00
..
doc	Adding the syntax and usage for cv2.undistortPoints().	2016-03-13 13:32:24 +01:00
include/opencv2	imgproc: Canny with custom gradient	2016-07-19 17:15:36 +03:00
misc/java	Java wrapper for moments: do not truncate values in set method	2016-03-31 12:57:10 +03:00
perf	Visual Studio 2015 warning and test fixes	2015-10-20 12:48:37 +03:00
src	Make goodFeaturesToTrack() return deterministic results	2016-07-25 21:17:54 -07:00
test	imgproc test: Canny with custom gradient	2016-07-19 17:15:36 +03:00
CMakeLists.txt	Python support	2015-03-02 18:13:00 +03:00