Chiebot-Mirror
/
opencv
mirror of https://github.com/opencv/opencv.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
Open Source Computer Vision Library https://opencv.org/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
14915 Commits
6 Branches
128 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: f83a76cdeb
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f83a76cdeb'
${ noResults }
Go to file
Brian Park f83a76cdeb
add input paramter checking that verifies the existance of the input files to stero_match example 		10 years ago
3rdparty Fixing iOS clang warnings, part 3 10 years ago
apps Several type of formal refactoring: 11 years ago
cmake Fixing iOS clang warnings, part 3 10 years ago
data moved part of video to contrib/{outflow, bgsegm}; moved matlab to contrib 11 years ago
doc fixed some more compile errors and test failures 10 years ago
include Split highgui module to videoio and highgui 11 years ago
modules Merge pull request #3352 from alucarded:BackgroundSubtractorMOG2_optimization 10 years ago
platforms Fixing iOS clang warnings, part 3 10 years ago
samples add input paramter checking that verifies the existance of the input files to stero_match example 10 years ago
.gitattributes
…
.gitignore Merge remote-tracking branch 'origin/2.4' into merge-2.4 11 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt Merge pull request #3332 from lupustr3:pvlasov/implementation_detector 10 years ago
LICENSE adding LICENSE file and a sample of its reference in ocl.hpp 11 years ago
README.md Replaced Gittip button 11 years ago
index.rst GSoC Python Tutorials 12 years ago

README.md

OpenCV: Open Source Computer Vision Library

Gittip

Resources

Contributing

Please read before starting work on a pull request: http://code.opencv.org/projects/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.