Using OpenCV 2.3.1 with Visual Studio 2010 (tutorial)

Here in this tutorial I am going to show how to configure Visual Studio 2010 to use OpenCV 2.3.1 in your computer vision projects. Also, I am going to write a couple of lines of code to show new OpenCV C++ API.

By the time the tutorial was written the latest version of OpenCV was 2.3.1. The methods described below should, but may not, work for different versions. This tutorial targets computer vision course students at Computer Engineering in BOUN, but I will be generalizing as much as I can, so everyone can enjoy it.

Foreword

Before starting I would like to suggest a couple of things.

First, if you are ever going to write C++ code, read Effective C++, 3rd edition by Scott Meyers (CAUTION! 2nd edition is outdated, it is not worth reading imho). This book has many topics on how to write correct, working, easily maintainable C++ code. I see lots of boilerplate code around when it comes to C++, not only reading this book will reduce such practices, it will save you time. Besides, you will feel healthy mind-wise :) If there was to be only one book on C++, and the rest was to disappear, I would select this book. Be careful though, this book is *NOT* for beginners, you need to know a little bit of C++ to understand what it means.

Effective C++ 3rd edition

For BOUN students who are taking Computer Vision course, the book is available as an electronic resource in the library.

Second, Google has really good guidelines on different programming languages, including C++. Although they are specialized for their internal use, I recommend following those guidelines. The guideline provide the motivation behind the rules, so it is also great place to learn how to write C++ properly. Again, it is not a place to learn C++, but to master C++.

Preparation

Make sure that you have Visual Studio 2010 (VS2010) installed.

For BOUN students, it is available in license server. I don’t quite know the details, you may need to work it on your own.

Download OpenCV 2.3.1 and extract the contents to a folder. I prefer to put directly under root like “C:\OpenCV-2.3.1\”.

Optionally, I recommend using Visual Assist X to write and refactor code easily.

Configuring VS2010

There are a couple of ways to configure Visual Studio 2010, I am going to show a way which I find convenient. We are going to configure it using property sheets. Whenever we need to create another project, we just need to add same property sheets to new project. Let’s start.

Launch VS2010 and select “New project…”.

Select “Empty Project”, enter “hello-opencv” as Name, select a location to place project. I also prefer, for simplicity, not creating directory for solution so I unchecked that option. See the image below.

When done, press “OK”.

Now we have created a project from scratch. It is time to link the libraries and make our project use OpenCV.

Switch to Property manager by clicking on the tab below.

The default properties are for 32-bit systems (note the Win32 suffixes), because I am using 64-bit system, from now on I am going to describe the configuration for 64-bit systems.

From the “Build” menu, select “Configuration Manager”. Under “Active solution platform” Win32 should be selected by default. Click on it and select “New…”.

Select “x64″ as the new platform and select Win32 to copy settings from. Make sure that “Create new project platforms” is checked.

Now your Property Manager view should look like this:

Select the Win32 configurations and delete them, you won’t be needing those. Let me remind this one more time, these steps are only required if you are using 64-bit system and want to develop 64-bit applications.

To add a property sheet right click on “Debug | x64″ and select “Add New Project Property Sheet”. This property sheet will/should only include the details on how to link the OpenCV library to our project. Once this is done, the property sheet can be shared between projects on the same computer.

On the add new property sheet dialog, I entered “OpenCV-Debug” as the sheet name, because this sheet will link debug libraries. After pressing “Add” the new property sheet will show up in Property Manager. Double click on it, a dialog with lots of properties will be shown.

Under “Common Properties” -> “C/C++” -> “General”, edit “Additional Include Directories” and add “C:\OpenCV-2.3.1\build\include”. Of course don’t forget to change the path accordingly if you have put OpenCV files to a different place. It is important that you select the “include” folder under “build” folder, not any other “include” folder.

Under “Common Properties” -> “Linker” -> “General”, edit “Additional Library Directories” and add “C:\OpenCV-2.3.1\build\x64\vc10\lib”. I won’t tell you to change the path to your OpenCV path next time :) Here “x64″ stands for 64-bit systems, if you are using 32-bit change it to x86. “vc10″ stands for Visual C++ 2010, leave it as it is assuming you are using VS2010.

Under “Common Properties” -> “Linker” -> “Input”, edit “Additional Dependencies” and add the following lib files:

opencv_calib3d231d.lib
opencv_contrib231d.lib
opencv_core231d.lib
opencv_features2d231d.lib
opencv_flann231d.lib
opencv_gpu231d.lib
opencv_haartraining_engined.lib
opencv_highgui231d.lib
opencv_imgproc231d.lib
opencv_legacy231d.lib
opencv_ml231d.lib
opencv_objdetect231d.lib
opencv_ts231d.lib
opencv_video231d.lib

Actually you won’t probably need all the libraries. Linking the only necessary ones may make linking operation a little bit faster but for our case, that speed up is not worth the effort. Note the letter “d” in filenames just before the dot, that “d” stands for “Debug”.

The steps are the same for “Release” configuration except the linked library filenames. You just need to get rid of the “d” letters before the dot. Debug libraries includes additional instructions for debugging purposes such as variable watching, and they are not optimized. This makes debug libraries run slower. When you are dealing with lots of data or you just need more processing power you should switch to release configuration which is free of extra instructions and optimizes your code, hence runs much faster.

Hello OpenCV

OK. Now we are (almost) ready to write our first lines of code. Switch to “Solution Explorer” by clicking the tab below. Right click on “Source Files”, select “Add” -> “New Item…”. Select “C++ File” from the menu and type “main” as name.

Insert the following lines into the main.cpp and run the code (press F5).

#include <opencv2/opencv.hpp>

using namespace cv;

int main()
{
    Mat img(Mat::zeros(100, 100, CV_8U));

    imshow("window", img);

    waitKey();

    return 0;
}

You should get an error about a missing dll. Locate “hello-opencv.exe” in your project folder. Copy the dll files (preferably the ones that ends with letter “d”) from “C:\OpenCV-2.3.1\build\x64\vc10\bin” to that folder.

By the way, using full namespaces like “using namespace cv;” is discouraged. I recommend using “using cv::Mat;”, this will prevent name collisions and make the code more maintainable. See this discussion for details.

Some people prefer adding these dll into PATH environment variable, I prefer my projects to be self sufficient. It is good to be in control of which dll the project is using. If you are dealing with multiple projects using the different versions of the same library, if the dll names are the same, PATH approach will not work.

Run the code again. It should work fine and display a 100×100 black image in a window. If not that means there is a problem that you need to figure out. Try until you solve that problem.

Now modify the main.cpp so it is like:

#include <opencv2 /opencv.hpp>

using namespace cv;

int main()
{
    Mat img;
    VideoCapture cap(0);

    while (true)
    {
        cap >> img;

        Mat edges;
        cvtColor(img, edges, CV_BGR2GRAY);

        Canny(edges, edges, 30, 60);

        imshow("window label", edges);
        waitKey(1);
    }

    return 0;
}

The code above needs a webcam connected to the computer, it captures images from a camera.

And run the code. You should get a missing “tbb_debug.dll” error. This is a bug of OpenCV-2.3.1. It should be shipped with tbb_debug.dll but it is missing in the package. That dll is the part of Threading Building Blocks project by Intel, you should download the latest version from here. The zip file that you have downloaded contains the dll, and you should copy that dll to the same folder under your project like other dlls (same directory as hello-opencv.exe).

Now run the code again. “Canny” is an edge detection algorithm, if the program runs well, you should see the detected edges of the captured image.

This completes our tutorial.

Closure

The documentation of OpenCV is quite good. Use it extensively.

I highly recommend using new OpenCV C++ API. The new API is clean, slick and well-designed. Avoid using old API, e.g. IplImage, unless you really know what you are doing. There are lots of information on internet about OpenCV which is outdated, beware of those. Always use the latest official documentation first.

Goruntuyu yeniden boyutlandirma

OpenCV ekolunden geldigim icin Java’nin goruntu isleme icin kullandigi akis ilk asamada oldukca karmasik geldi. OpenCV ile goruntu islemeye devam etmememin nedeni 6 ay kadar Java kullandiktan sonra muptelasi oldugum C++’ tan tiksinmem. Yok memory allocation, yok referansla const mu gonderecez parametreyi gibi kistaslar kafa yorgunlugundan baska bisey yapmiyordu. E tabi yeni bir dille beraber onun kendine has sorunlari basgosterdi. Neyse efenim konumuza geri donelim. Bir image’i resize etmeye calisirken neler ogrendik?

  1. Image.getScaledInstance() kullanmak pek hayirli degil.
    Sonuclar guzel olsa da performans o kadar dusuk ki, scalable hic degil.
  2. Graphics.drawImage() downsampling yaparken pek guzel sonuclar vermiyor.
    Ne kadar anti-aliasing yaparsaniz, rendering quality arttirsaniz da yine de kirpik kirpik gorunuyor kenarlar.
  3. AffineTransform.scale() ile resize etmek yerine tek satirda Graphics.drawImage() ayni isi yapabiliyorsunuz.
  4. JAI kullanmak da kaliteyi arttirmada pek fayda saglamiyor.

Peki durum boyleyken en duzgun resize etme nasil olacak? Hos kalitesiz downsampling benim isimi cok etkilemiyordu cunku bilgisayarli goru ile ugrasiyorum, insanlara sunacak bi resim uretmiyorum, ama yine de gun gelir ihtiyacim olur diye paylasayim.

Graphics.drawImage() eger giris goruntusunu yariya kadar kucultecekseniz ise yariyor, yaridan fazla kucultecekseniz (ornegin 1/3 oraninda) kalitesiz sonuc veriyor.
O halde istedigimiz kucultme oranina yaklasana kadar yarim yarim kucultecegiz, yaklastigimizda ise istedigimiz oranda kucultecegiz.
Ornegin 500×500 boyutlarinda bir goruntuyu 100×100 boyutlarina kuculteceksek ilk once 250×250 boyutlarina, ardindan 125×125 boyutlarina, son olarak da 100×100′e kucultuyoruz.

Goruntuyu buyultmek istiyorsak zaten sorun yok, bir seferde isimizi gorebiliyoruz.

Diyosaniz ki benim server’da kaynak bol, optimizasyon umrumda degil Image.getScaledInstance() kullanin efendim. Ya da tek seferde kucultup uzerine bi de hafiften blur atin.

Enfes kaynak: The Perils of Image.getScaledInstance() – Chris Campbell

Basit JavaShell

Giriş

JavaShell classı basit bir Java command line interface ile programdaki belirli fonksiyonlari direkt cagirabilmek icin bir ornektir.

Kullanım

method = JavaShell.class.getMethod(cmd, new Class[] {});
method.invoke(JavaShell.class, new Object[] {});
ile bulundugu class icindeki metodlar direkt cagrilabilir. Onemli kisit metodlarin public deklare ediliyor olma gereksinimidir. Public olmayan metodlara erisim icin kullanilamaz.

Örnek

JavaShell V01 by Keyholder
Date:Sun Feb 24 01:18:50 EET 2008
$>
olmayan_metod
Command not found
$>
exit
Bye bye

Download

JavaShell

Google OCR veri seti

OCR charactersDaha önce OCR sistemlerinizi test etmek ya da eğitmek için kullanabileceğiniz sınırlı bir karakter verisetini burada paylaşmıştım.

Verisetine ihtiyaç duyanlar bunları elde etmenin ne kadar zor olduğunu bilirler. Hayat kurtarıcı sürpriz Google’dan geldi. ICDAR2007‘de (Uluslararası Döküman Analiz ve Tanıma Konferansı) konuşmacı olarak yer alan Luc Vincent’ın müjdelediğine göre, Google şimdiye kadar Google Book Search sürecinde elde ettikleri, telif hakkı olmayan, verileri bir araya getirip araştırmacılar için kapsamlı bir veriseti hazırlama sürecine girmiş.

İlk ürünleri bir an evvel alabilmemiz umuduyla.

Kaynak: Google Book Search: Document Understanding on a Massive Scale, Vincent L.

Java Karakter Sayaci

Harflerin sayi gibi muamele gormesi icin hazirlamis oldugum java methodu. Bir vakit yazdigim bir test simulatorunde string test serileri uretmek icin kullanmis idim.

Ornekler:

a verilir , b alinir
aab verilir, aac alinir
daz verilir , dba alinir
bzz verilir , caa alinir
zz verilir, aaa alinir

StringCounter.java

Bölütlenmiş Karakterler v0.1

Bölütlenmiş karakterler, optik karakter tanıma(OCR) gibi uygulamalarınızda test/eğitim amacıyla kullanılabilecek 0-9 arası rakam ve büyük harflerden oluşan bir veri setidir. Veriler gerçek dünyadan edinildiği için veriler gürültülüdür.
An itibariyle hayli eksik olduğundan varolan veri setinizi genişletmek amacıyla kullanabilirsiniz.
Yanlışlıkları bitkidoku *AT* anlak *NOKTA* com eposta adresine bildirirseniz sevinirim.
Verisetinden örnekler:
3 G M P

Hangi karakterden kaç adet var?

Karakter Adet
0 100
1 114
2 131
3 92
4 111
5 92
6 102
7 87
8 124
9 105
A 191
B 70
C 69
D 4
E 6
Karakter Adet
F 1
G 3
H 31
K 92
L 6
M 58
N 5
O 4
P 47
T 26
V 1
X 144
Y 4
Z 2
. .

toplam: 1821


Internet uzerinde bulunan benzer veri setlerinden bazilari: