OSSForks/opencv
1
0
Fork 0
mirror of https://github.com/zebrajr/opencv.git synced 2025-12-06 12:19:50 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library opencv.org
27,032 Commits 6 Branches 116 Tags 598 MiB
C++ 87.5%
C 3.1%
Python 3%
CMake 2%
Java 1.5%
Other 2.7%
8ac333697d
Go to file
Dizhenin Vlad 8ac333697d
Merge pull request #16853 from SimpleVlad:note 
Add link to article for sample "Intelligent scissors"

* Add link to article

* Add autors name

* Fix whitespace
2020-03-19 21:39:54 +00:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty ffmpeg/3.4: update FFmpeg wrapper 2020-03-10 19:05:50 +00:00
apps opencv_version: dump threads information 2020-03-12 16:41:03 +03:00
cmake core: adjust type of allocator_stats counter, allow to disable 2020-03-11 20:12:29 +03:00
data Some mist. typo fixes 2018-02-07 06:59:15 -05:00
doc Merge pull request #16818 from iteal:master 2020-03-18 08:45:09 +00:00
include add missing DNN header to opencv2/opencv.hpp 2018-02-15 15:59:14 +01:00
modules Merge pull request #16828 from paroj:nmspy 2020-03-19 16:43:43 +00:00
platforms pre: OpenCV 3.4.10 (version++) 2020-03-10 14:53:43 +03:00
samples Merge pull request #16853 from SimpleVlad:note 2020-03-19 21:39:54 +00:00
.editorconfig add .editorconfig 2018-10-11 17:57:51 +00:00
.gitattributes cmake: generate and install ffmpeg-download.ps1 2018-06-09 13:19:48 +03:00
.gitignore Ignore Visual Studio cmake configuration file 2020-03-17 21:12:54 +03:00
CMakeLists.txt Merge pull request #16724 from liqi-c:3.4-tengine 2020-03-09 14:59:23 +00:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE copyright: 2020 2020-01-02 11:58:20 +00:00
README.md 3.4 docs for 3.4 branch 2020-02-11 09:31:16 +03:00

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read the contribution guidelines before starting work on a pull request.

Summary of the 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.