Go to file
Miroslav Benes 5b1fd739d9 Add Triangle thresholding algorithm
Add Triangle method for automatic threshold computation next to the existing
Otsu's method. Triangle deals better with images whose histogram does not
contain dominant peak.

See paper Zack GW, Rogers WE, Latt SA.: Automatic measurement of sister
chromatid exchange frequency. J Histochem Cytochem. 1977 Jul;25(7):741-53.
2014-10-22 16:54:39 +02:00
3rdparty Fixing iOS clang warnings, part 3 2014-10-17 18:15:21 +04:00
apps Several type of formal refactoring: 2014-08-13 15:21:35 +04:00
cmake Fixing iOS clang warnings, part 3 2014-10-17 18:15:21 +04:00
data moved part of video to contrib/{outflow, bgsegm}; moved matlab to contrib 2014-08-10 23:24:16 +04:00
doc fixed some more compile errors and test failures 2014-10-17 15:02:56 +04:00
include Split highgui module to videoio and highgui 2014-07-14 23:16:47 +04:00
modules Add Triangle thresholding algorithm 2014-10-22 16:54:39 +02:00
platforms Fixing iOS clang warnings, part 3 2014-10-17 18:15:21 +04:00
samples quickly corrected the previous refactoring of features2d: moved from set(SOME_PROP, val) to setSomeProp(val) 2014-10-18 20:44:26 +04:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-01-14 11:53:59 +04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt Merge pull request #3332 from lupustr3:pvlasov/implementation_detector 2014-10-16 14:51:53 +00:00
index.rst GSoC Python Tutorials 2013-09-23 13:41:14 +05:30
LICENSE adding LICENSE file and a sample of its reference in ocl.hpp 2013-12-18 19:33:25 +04:00
README.md Replaced Gittip button 2014-02-15 13:10:09 +04:00

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.