2014-10-31 15:36:26 -0600 | received badge | ● Teacher (source) |
2013-11-14 06:23:15 -0600 | commented answer | knnMatch gives wrong number of neighbours I also had issues with vector<vector<DMatch>> objects that disappeaed by changing my IDE parameters. So I would definitely believe that it was the use of the VC10 files. |
2013-11-12 17:49:45 -0600 | received badge | ● Editor (source) |
2013-11-12 17:49:08 -0600 | answered a question | knnMatch gives wrong number of neighbours I found a solution when I changed some IDE parameters and when updating to OpenCV 2.4.7. So the solution was:
|
2013-11-11 17:40:27 -0600 | received badge | ● Supporter (source) |
2013-11-11 17:19:10 -0600 | received badge | ● Critic (source) |
2013-10-29 09:08:51 -0600 | answered a question | matcher tutorial I would link to another post with good answer on how to refine matches : http://stackoverflow.com/questions/8118825/how-to-reduce-matches-in-opencv-pattern-recognition There are several ways to improve the matching performances, basically by making sure that the matches you have found are reliable. I think this is the way to go, rather than trying to improve the preprocessing on your images. |
2013-10-28 08:52:44 -0600 | received badge | ● Necromancer (source) |
2013-10-28 02:15:19 -0600 | answered a question | Object recognition knnmatch knnMatch outputs the list of k nearest neighbours as a vector<vector<dmatch>>. It means that for each feature in the query image, it will output k (or less) DMatch, hence the need for a 2D structure. If you only need 1 neighbour for each query image feature, you can use the .match() method, with the output as a vector<dmatch>. |
2013-10-27 20:28:41 -0600 | asked a question | knnMatch gives wrong number of neighbours Hello everyone, I have an issue implementing one recipe from the book "OpenCV 2 Computer vision Application Programming" that I see around, which uses knnMatch. Here is the code I use: When I run this code, I obtain the following text in my console: What I do not understand, is why some elements of the Vector matches_multiple_1 and _2 have not the right size, notably, the zero value and the very large values. I tried to go back from scratch several ... (more) |