2013-07-10 03:22:46 -0600 | received badge | ● Teacher (source) |
2013-07-09 13:06:08 -0600 | answered a question | How to zoom in and out in open cv? I am new for open cv so ,I request you to guide me You are probably searching for the function |
2013-07-06 12:30:41 -0600 | answered a question | Imread causing fatal error on the program Your code works fine for me. I've tested it on Linux (Ubuntu 12.04, 64 bit) with OpenCV 2.4.5. Maybe the image file isn't located where the application expects it to be? However, here are some recommendations:
Here's my Code: HTH |
2013-07-06 09:58:58 -0600 | answered a question | Bug in GPU_SURF and OpenCV's OpenCL module? Nevermind, I found a solution to the first issue: My application requires the key points to be sorted according to their response. While the CPU version does it automatically, the GPU versions don't. Unfortunately, I accidentally sorted (only) the key points but not the corresponding descriptors. Clearly, this caused a mismatch when indexing collected key points and descriptors in the training phase of my SVM. IIRC, the problem arised somehow from the (OCL module) documentation which state:
Even if this is somehow true, there are some essential differences which aren't documented (well) (e.g., the CPU version performs a sorting while the GPU versions don't). In addition, it should be noted that there are some differences between CPU and GPU when comparing the descriptors (see also here). This is due some implementation aspects of the GPU. However, at least in my application, these differences seem to be acceptable. I hope it helps someone else in avoiding this pitfall. Note, however, using the |
2013-07-02 18:33:35 -0600 | received badge | ● Editor (source) |
2013-07-02 18:31:50 -0600 | asked a question | Bug in GPU_SURF and OpenCV's OpenCL module? Hi all, I am using the CUDA-based SURF implementation to extract key points in real-time. Afterwards, the properties (response value and some specific entries of the description vector) of the key points are used as features for SVM classification. The CPU version of OpenCV's SURF implementation works as expected. However, both GPU variants (CUDA and OpenCL) do not because the entries of the description vectors differ w.r.t the CPU version. As a consequence, my SVM yields bad classification results which is shown by the following figures: The first 2 figures show the training results (decision boundary/support vectors and training samples of both classes) for the CPU version and the last 2 figures show the results of the OpenCL version, respectively (... for the same input, of course). For example, the first 10 entries of the
whereas the
The CUDA variant (
However, the detector responses are identical in all 3 versions. BTW: The ctor of Another OpenCL related problem is also described here. In short: All apps (incl. the official samples) using
Looks like someone accesses a 0-ptr?! Note that just calling Any help/hints is highly appreciated! Thanks in advance! :-) Setup:
PS: If you need more information, just ask! ;-) EDIT: Formatting issue fixed. UPDATE: The OCL crash seems to be a known bug, see http://code.opencv.org/issues/3120 . |
2013-07-02 18:18:24 -0600 | answered a question | Glibc detected I cannot see any problems in your code. The issue have to be related to calling You should use a debugger (with the However, this problem does not seem to be OpenCV-related. HTH ;-) |