mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-28 21:20:18 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
19,117 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
a2b353d178
Go to file
berak a2b353d178 Update non_linear_svms.cpp 
fix for #6598
2016-05-30 06:56:28 +02:00
.github move GitHub templates into .github folder 2016-03-04 14:20:25 +03:00
3rdparty Updates for XCode 7.3 2016-04-17 20:21:29 +03:00
apps add a cascade classifier model visualisation tool for master branch 2016-05-11 08:56:42 +02:00
cmake Fix #6500 cmake bug that adds D_FORCE_INLINES to NVCC 2016-05-26 13:45:50 +03:00
data Fix the missing - in file. 2016-02-18 11:28:41 +01:00
doc fixed "tot_error" to "mean_error" & nicer whitespace 2016-05-17 20:00:28 +02:00
include include available modules only 2016-01-20 13:07:46 +03:00
modules Merge pull request #6589 from tomoaki0705:fixThresh64fTest 2016-05-26 12:44:56 +00:00
platforms Added --extra_modules_path to build_sdk.py 2016-05-12 12:36:42 +03:00
samples Update non_linear_svms.cpp 2016-05-30 06:56:28 +02: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 Restored cmake 2.8.7 support 2016-05-18 13:20:21 +03: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.