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.
19806 Commits
7 Branches
128 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: a12207c3ad
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a12207c3ad'
${ noResults }
Go to file
Francisco Facioni a12207c3ad
LSD: Avoid using pointers directly, image could be non continuous 		9 years ago
.github migration: github.com/opencv/opencv 9 years ago
3rdparty Merge pull request #7208 from terfendail:openvx_hal_impl 9 years ago
apps Merge pull request #7278 from alalek:opencv_version 9 years ago
cmake Merge pull request #7266 from alalek:pr7159 9 years ago
data Removing whitespace to appease doc builder 9 years ago
doc Merge pull request #7112 from StevenPuttemans:improve_cascadeclassifier_training_tutorial 9 years ago
include fix inclusion of OpenCV header opencv.hpp 9 years ago
modules LSD: Avoid using pointers directly, image could be non continuous 9 years ago
platforms Fix android libc++ build 9 years ago
samples supress numpy future warning with `None` comparison 9 years ago
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 12 years ago
.gitignore Improved thrust interop tutorial. 10 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt Merge pull request #7266 from alalek:pr7159 9 years ago
CONTRIBUTING.md migration: github.com/opencv/opencv 9 years ago
LICENSE Update license year range to 2016 9 years ago
README.md migration: github.com/opencv/opencv 9 years ago

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read before starting work on a pull request: https://github.com/opencv/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.