2014-06-28 04:51:36 -0600 | received badge | ● Student (source) |
2014-06-27 12:12:35 -0600 | asked a question | Different recognition results by SURF on CUDA and OpenCL I use both three SURF algorithm implementation in the program. When I conducted the tests I noticed that the algorithm using OpenCL detect much smaller objects in the image than that on CUDA. What may be the reason? Anybody notice like that? Implementation of algorithms written by different people, can differ in the implementation of the algorithms? P.S. All parameters are the same sets of reference images too. I can provide code samples and processing results. |
2014-05-19 05:55:56 -0600 | asked a question | Russian books or articles about Viola Jones & AdaBoost algorithm I apologize for the issue is not explicitly linked OpenCV. For my thesis I need to complete mathematical description of these algorithms in the literature in Russian. If anyone met similar would be very grateful. I can also share a set of books and articles (~ 4GB) on the topic of computer vision. |
2014-04-11 06:54:08 -0600 | asked a question | Manual selection of OpenCL adapter In my configuration, I have a few (2-8) ATI adapters. From config specific DeviceId know which I need to connect to. How can I do it in code? |
2013-07-24 04:22:11 -0600 | commented answer | Strange assert in surf_gpu.cpp Thanks for the proof. Then maybe we should change the line 131 to const int min_margin = 11; |
2013-07-24 02:35:33 -0600 | commented answer | Strange assert in surf_gpu.cpp I solved the problem with the small image size. But why line 131 returns always 11? =) |
2013-07-23 14:46:21 -0600 | asked a question | Strange assert in surf_gpu.cpp I get very strange asserts in my code, changing the size of the input image. Line 125 surf_gpu.cpp opencv 2.4.5 I decided to read the code and came across a black magic Code (line 131): gives always 11 proof: this is bug or not? |
2013-04-24 06:01:53 -0600 | commented answer | Bug or not bug? knnMatch from BruteForceMatcher_GPU Thank you for help! It work! |
2013-04-23 08:29:34 -0600 | commented answer | Bug or not bug? knnMatch from BruteForceMatcher_GPU Thank you for answer! It`s cool! But this check did not work
My function gives a result for the corners of the result border:
|
2013-04-23 08:21:53 -0600 | received badge | ● Scholar (source) |
2013-04-23 08:21:46 -0600 | received badge | ● Supporter (source) |
2013-04-23 08:01:18 -0600 | commented question | Bug or not bug? knnMatch from BruteForceMatcher_GPU Hmm.. I'll try it. How can I download descriptors from ORB_GPU? In my code I used |
2013-04-23 06:45:26 -0600 | received badge | ● Editor (source) |
2013-04-23 06:44:07 -0600 | asked a question | Bug or not bug? knnMatch from BruteForceMatcher_GPU There is a problem of the match decriptors on the GPU. OpenCV 2.4.5, CUDA 5.0 I tried to transfer my SURF matcher from the CPU to the GPU and got such a strange result. I use knnMatch and findHomography + perspectiveTransform together with my function, which checks the corners of the bounding box for the result to more precision. GPU part: Bad result on GPU (MIN_HESSIAN==1500): Bad result on GPU (MIN_HESSIAN==400): CPU part: (more) |
2013-04-04 03:31:00 -0600 | asked a question | Create Haar classifier using CUDA Hi! I have a video card Tesla k20c, can I quickly get a cascade using GPU computing? |