Tag: Branch: Tree: 88b28ee2a0

2.4

3.4

4.x

5.x

master

next

2.2

2.3.0

2.3.1

2.4.0

2.4.1

2.4.10

2.4.10.1

2.4.10.2

2.4.10.3

2.4.10.4

2.4.11

2.4.12

2.4.12.1

2.4.12.2

2.4.12.3

2.4.13

2.4.13.1

2.4.13.2

2.4.13.3

2.4.13.4

2.4.13.5

2.4.13.6

2.4.13.7

2.4.2

2.4.3

2.4.3-rc

2.4.3.1

2.4.3.2

2.4.4

2.4.4-beta

2.4.5

2.4.6

2.4.6.1

2.4.6.2

2.4.6.2-rc1

2.4.6.2r2

2.4.6.2r3

2.4.7

2.4.7-rc1

2.4.7.1

2.4.7.2

2.4.8

2.4.8.1

2.4.8.2

2.4.8.3

2.4.9

2.4.9.1

3.0-ocl-tech-preview

3.0-ocl-tp2

3.0.0

3.0.0-alpha

3.0.0-beta

3.0.0-rc1

3.1.0

3.2.0

3.2.0-rc

3.3.0

3.3.0-cvsdk

3.3.0-rc

3.3.1

3.3.1-cvsdk

3.4.0

3.4.0-rc

3.4.1

3.4.1-cvsdk

3.4.10

3.4.11

3.4.12

3.4.13

3.4.14

3.4.15

3.4.16

3.4.17

3.4.18

3.4.19

3.4.2

3.4.2-openvino

3.4.20

3.4.3

3.4.3-openvino

3.4.4

3.4.5

3.4.6

3.4.7

3.4.8

3.4.9

4.0.0

4.0.0-alpha

4.0.0-beta

4.0.0-openvino

4.0.0-rc

4.0.1

4.0.1-openvino

4.1.0

4.1.0-openvino

4.1.1

4.1.1-openvino

4.1.2

4.1.2-openvino

4.10.0

4.10.0-kleidicv

4.11.0

4.2.0

4.2.0-openvino

4.3.0

4.3.0-openvino

4.3.0-openvino-2020.3.0

4.4.0

4.4.0-openvino

4.5.0

4.5.0-openvino

4.5.1

4.5.1-openvino

4.5.2

4.5.2-openvino

4.5.3

4.5.3-openvino

4.5.3-openvino-2021.4.1

4.5.3-openvino-2021.4.2

4.5.4

4.5.5

4.5.5-openvino-2022.1.0

4.6.0

4.7.0

4.8.0

4.8.1

4.9.0

5.0.0-alpha

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '88b28ee2a0'

${ noResults }

Commit Graph

4 Commits (88b28ee2a0fec46029d6e07a946cc3ee853ab1ab)

Author	SHA1	Message	Date
Maksim Shabunin	f9e9567870	Merge pull request #25424 from mshabunin:fix-features2d-test ... features2d: reduce accuracy test avg memory consumption #25424 **Merge with contrib**: https://github.com/opencv/opencv_contrib/pull/3722 I've observed high memory consumption in the `opencv_test_features2d` (x86_64, Ubuntu 22.04, Debug):  It's always more than 180 MiB with peak at 535 MiB This was caused by pointers to the algorithm object instances stored in the tests parameters. I've replaced them with factory functions/lambdas with the following result:  Now peak is at 355 MiB and permanent consumption level is ~ 1-2 MiB **Note:** current peak is caused by KAZE features allocating 8x image size utility buffers. Not sure if we can or should do anything about it: 66fb5021e9/modules/features2d/src/kaze/KAZEFeatures.cpp (L61-L68)	10 months ago
Tomoaki Teshima	35245cb76e	fix test failure on Mali T760 and Mali T628	5 years ago
Alexander Alekhin	4a297a2443	ts: refactor OpenCV tests ... - removed tr1 usage (dropped in C++17) - moved includes of vector/map/iostream/limits into ts.hpp - require opencv_test + anonymous namespace (added compile check) - fixed norm() usage (must be from cvtest::norm for checks) and other conflict functions - added missing license headers	7 years ago
Jiri Horner	a5b5684670	Merge pull request #9330 from hrnr:akaze_ocl ... [GSOC] Enable OCL for AKAZE (#9330) * revert e0489cb - reenable OCL for AKAZE * deal with conversion internally in AKAZE * pass InputArray directly to AKAZE to allow distiguishing input Mat/UMat. deal with conversion there * ensure that keypoints orientations are always computed. prevents misuse of internal AKAZE class. * covert internal AKAZE functions to use InputArray/OutputArray * make internal functions private in AKAZE * split OCL and CPU paths in AKAZE * create 2 separate pyramids, 1 for OCL and 1 for CPU * template functions that use temporaries to always store them as correct type (UMat/Mat) * remove variable used only in OCL path causes unused variable warning * update AKAZE documentation * run ocl version only when ocl is enabled * add tests for OCL path in AKAZE * relax condition for keypoints angle	8 years ago