3 ms·
I don't see any problem with the original solution. It is classic (but little bit old fashioned) way of detecting objects, far from random. I also think that yo
by buq2 14y ago
I don't see any problem with the original solution. It is classic (but little bit old fashioned) way of detecting objects, far from random. I also think that you oversimplify the SIFT solution. You use sift, then what? Match the feature vectors, get bunch of possible correspondence points, prune outliers using 3D model of a cylinder (or assume that the face of the can is flat plane and just use homography) and robust fitting, validate fitting, find other cans, if none found change parameters? No preprocessing? Ignore color? Etc. Not so straight forward.
SIFT is faster than generalized HoughTF in this case, use of points instead of whole objects/blobs gives you nice ways to validate using 3D model, etc., but I would still not look down on some one who finds and implements this solutions as a student.
- strebler 14y agoYou're right, it's ok for a project. I guess what I meant was it's quite easy compared to the problems my company deals with every day. 30 images in 24 hours (I think it said) is kind of a problem. Given the constraints of the asker (all available in OpenCV), the solution I would suggest first is SIFT + homography, both easy to use and in OpenCV (sample code is around). Yes, there's a lot of other possibilities, but this would be an improvement over the original.