Go to file
Pavel Rojtberg 22b64e2c28 CvLevMarq: remove fixed rows instead of setting them to zero
use the same approach like in fisheye calibration: instead of setting
masked out rows to zero, remove them from the equation system.
This way JtJ does not become singular and we can use the much faster LU
decomposition instead of SVD.

This results in a speedup of the Calibrate unit tests of 3x-10x.
2015-12-10 23:02:18 +01:00
3rdparty Merge 2.4 into master 2015-12-08 10:24:54 +03:00
apps Merge pull request #5757 from alalek:merge-2.4 2015-12-08 11:51:29 +00:00
cmake Merge pull request #5757 from alalek:merge-2.4 2015-12-08 11:51:29 +00:00
data move data/detect_blob.png in samples/data 2015-06-22 17:51:01 +02:00
doc fixed whitespace 2015-12-07 22:06:08 +02:00
include Added cmake option for abi descriptor generating (GENERATE_ABI_DESCRIPTOR) 2015-03-17 16:04:04 +03:00
modules CvLevMarq: remove fixed rows instead of setting them to zero 2015-12-10 23:02:18 +01:00
platforms New variant of iOS framework building, fixed some warnings for XCode 7.1.1 and cmake 3.3.2 2015-11-17 15:30:01 +03:00
samples Merge 2.4 into master 2015-12-08 10:24:54 +03: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 Merge pull request #5757 from alalek:merge-2.4 2015-12-08 11:51:29 +00:00
CONTRIBUTING.md add link to contributing guidelines 2015-09-17 14:15:20 +02:00
LICENSE 1. Input/OutputArray optimizations; 2015-04-07 16:44:26 +03:00
README.md Update README.md 2015-08-06 14:00:24 +02:00

OpenCV: Open Source Computer Vision Library

Gittip

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.