h1. OpenCV Wiki

!http://opencv.org/wp-content/themes/opencv/images/logo.png!

OpenCV (Open Source Computer Vision) is a library of programming functions for the realtime computer vision. OpenCV is released under the liberal "BSD license":http://opensource.org/licenses/bsd-license.php and hence it's free for both academic and commercial use. It has C++, C, Python and Java (Android) interfaces and supports Windows, Linux, Android and Mac OS. The library has more than 2500 optimized algorithms. Adopted all around the world, OpenCV has more than 47 thousand people of user community and estimated number of downloads exceeding 5 million. Usage ranges from interactive art, to mines inspection, stitching maps on the web or through advanced robotics.

* "Wiki map":http://code.opencv.org/projects/opencv/wiki/index

h2. News

*04-Jul-2012* [[ChangeLog|OpenCV 2.4.2]] is out.

*04-Jul-2012* Welcome to our new sites http://opencv.org and http://answers.opencv.org!

h2. Resources

* Main OpenCV website: http://opencv.org. Old wiki page: http://opencv.willowgarage.com.

* OpenCV documentation: 

** Web: http://docs.opencv.org

** "Books":http://opencv.willowgarage.com/wiki/OpenCVBooks: "Learning OpenCV":http://www.amazon.com/Learning-OpenCV-Computer-Vision-Library/dp/0596516134 and the "OpenCV 2 Cookbook":http://www.packtpub.com/opencv-2-computer-vision-application-programming-cookbook/book.

** PDF: "Reference Manual":http://docs.opencv.org/opencv2refman.pdf, "Tutorials":http://docs.opencv.org/opencv_tutorials.pdf, "User Guide":http://docs.opencv.org/opencv_user.pdf, "Cheatsheet":http://code.opencv.org/projects/opencv/repository/raw/trunk/opencv/doc/opencv_cheatsheet.pdf.

* OpenCV user group (questions, support): http://tech.groups.yahoo.com/group/OpenCV.

* To get the *source code*, point your git client to git://code.opencv.org/opencv.git or to our public mirror git://github.com/itseez/opencv.git.

** If you need write credentials for OpenCV git repository, you should contact us via [email protected] (get rid of the ''delete-'' to make the emails work) and explain the situation.

h2. Issue Tracker

Please note that OpenCV project, as any open-source project, welcomes contributions from users. Either you have implemented some new functionality, or you're able to localize and fix a bug by yourself, please create a patch and share it with community. You should use _Patch_ tracker (issue type) for such contributions. Check your code for compliance with "OpenCV Code Style Guide":http://opencv.willowgarage.com/wiki/CodingStyleGuide and please explain how your piece of code could help other computer vision developers.

h3. Creating new tickets

You first need to register at http://code.opencv.org. If you had an account on OpenCV Trac system you should use your login with 'trac' password. You can change the password "here":http://code.opencv.org/my/account after the first login. Then:

* Click the "Issues":http://code.opencv.org/projects/opencv/issues tab or the "Search" box to look for existing tickets - probably your problem is already known or even fixed in the OpenCV trunk. If this is the case, please comment the ticket with your "+1". It will help us to select hot issues for the next iteration.

* If you can't find your problem on tracker, please click the "New issue":http://code.opencv.org/projects/opencv/issues/new tab to create a new ticket. _Bug_ and _Feature_ trackers are used for bug reports and feature requests respectively. *But you should use _Patch_ tracker if you have resolved the issue already and want to share the code.*

h3. Reporting bugs

* Please, specify your platform (Windows 32/64bit, Linux x86/x64/ppc/..., MacOSX 32/64bit/ppc); compiler version; OpenCV version/revision; whether IPP, OpenMP, MMX, SSE ... have been enabled or not, and any other information that let us reproduce the environment, identify and localize the problem.

* A sample code reproducing the problem helps us the most. Please check source://trunk/opencv/samples - for the preferred style (small code size, cross-platform).  There is *no need* to provide any project files or makefiles, if it is a short single-file sample, we could build it and run in a minute.

* If your application is complex, and the problem happens somewhere in the middle, often it is still possible to create a short standalone sample: 

** First, capture and store the data that you pass to the function using FileStorage.

** Then copy the function call and put the corresponding reading from FileStorage in front of it.

If we can reproduce the problem, we can fix it quickly.

h2. Topic Pages

* [[New functionality discussion]]

* [[Meeting_notes|Developer meeting notes]]