Home
last modified time | relevance | path

Searched refs:Hamming (Results 1 – 10 of 10) sorted by relevance

/external/opencv3/modules/features2d/test/
Dtest_descriptors_regression.cpp315 CV_DescriptorExtractorTest<Hamming> test( "descriptor-brisk", in TEST()
316 (CV_DescriptorExtractorTest<Hamming>::DistanceType)2.f, in TEST()
324 CV_DescriptorExtractorTest<Hamming> test( "descriptor-orb", in TEST()
326 … (CV_DescriptorExtractorTest<Hamming>::DistanceType)25.f, in TEST()
328 … (CV_DescriptorExtractorTest<Hamming>::DistanceType)12.f, in TEST()
344 CV_DescriptorExtractorTest<Hamming> test( "descriptor-akaze", in TEST()
345 … (CV_DescriptorExtractorTest<Hamming>::DistanceType)12.f, in TEST()
347 Hamming(), AKAZE::create()); in TEST()
/external/opencv3/doc/py_tutorials/py_feature2d/py_brief/
Dpy_brief.markdown22 strings are used to match features using Hamming distance. This provides better speed-up because
36 use Hamming Distance to match these descriptors.
/external/opencv3/modules/core/include/opencv2/core/
Dbase.hpp408 struct CV_EXPORTS Hamming struct
419 typedef Hamming HammingLUT;
/external/opencv3/doc/tutorials/features2d/akaze_matching/
Dakaze_matching.markdown67 We use Hamming distance, because AKAZE uses binary descriptor by default.
/external/opencv3/modules/flann/include/opencv2/
Dflann.hpp96 using ::cvflann::Hamming;
/external/opencv3/doc/py_tutorials/py_feature2d/py_matcher/
Dpy_matcher.markdown22 Hamming distance as measurement. If ORB is using WTA_K == 3 or 4, cv2.NORM_HAMMING2 should be
/external/opencv3/modules/flann/include/opencv2/flann/
Ddist.h415 struct Hamming
/external/opencv3/modules/flann/src/
Dminiflann.cpp332 typedef ::cvflann::Hamming<uchar> HammingDistance;
/external/opencv3/modules/features2d/src/opencl/
Dbrute_force_match.cl116 #elif (DIST_TYPE == 6) // Hamming
/external/opencv3/modules/core/src/
Dstat.cpp2486 Hamming::ResultType Hamming::operator()( const unsigned char* a, const unsigned char* b, int size )… in operator ()()