mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-24 19:20:28 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
19,219 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
0ed250cb5d
Go to file
Arthur Cinader 0ed250cb5d Implement PR feedback: 
1. Explain grayscale input still read as three channel
2. Fix typo
3. Add more details to image match explanation to include the use of masks
2016-07-11 15:21:47 -04:00
.github move GitHub templates into .github folder 2016-03-04 14:20:25 +03:00
3rdparty Update TBB 2016-06-23 11:48:48 +03:00
apps add a cascade classifier model visualisation tool for master branch 2016-05-11 08:56:42 +02:00
cmake cmake: fix install path 2016-06-28 13:29:00 +03:00
data Test data necessary for python samples added to test package. 2016-03-17 11:38:40 +03:00
doc Implement PR feedback: 2016-07-11 15:21:47 -04:00
include include available modules only 2016-01-20 13:07:46 +03:00
modules Merge pull request #6697 from wiryls:FileStorageBase64 2016-06-30 17:17:03 +00:00
platforms android: update build scripts 2016-06-20 15:15:21 +03:00
samples Implement PR feedback: 2016-07-11 15:21:47 -04:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Improved thrust interop tutorial. 2015-09-24 09:32:38 -04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt Merge pull request #6711 from Dubrzr:vs_compile_cuda_fix 2016-06-29 11:03:47 +00:00
CONTRIBUTING.md add link to contributing guidelines 2015-09-17 14:15:20 +02:00
LICENSE Update license year range to 2016 2016-01-18 10:11:01 +05:30
README.md Removed gittip link 2016-02-08 11:04:19 +03:00

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read before starting work on a pull request: https://github.com/Itseez/opencv/wiki/How_to_contribute

Summary of guidelines:

  • One pull request per issue;
  • Choose the right base branch;
  • Include tests and documentation;
  • Clean up "oops" commits before submitting;
  • Follow the coding style guide.