-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve blurry issue type #120
Comments
some more images flagged as blurry (source): |
I can confirm that blurred image detection gives way too many false positives, while the actual blurred ones are not even among the top ranks. The other issue types work much better. |
@saskra Thanks for the info! What sized images did you run on? We suspect some image sizes may not work well with our current blur check. It'd be helpful if you can share the results of "false positives" and "actual blurred ones" not detected!
|
This is a dataset of >7,500 smartphone photos of various resolutions, of which >500 were detected as blurry, even though it should be a low double-digit number. Unfortunately, I cannot publish the images. I also can't tell yet if the actual blurred images were not detected at all, I've only checked so far that they are not in the first hits. In fact, I haven't found a working alternative yet either, at best I can automatically detect the blurrier one between two very similar images. |
Interesting, well thanks for sharing the info you can! Our team is looking into improvements for blurry-detection, but it may be challenging to do via simple algorithms for every possible image domain. If you ever try it on other image datasets you have, do let us know how that worked! |
In my previous company, I used this one and it worked perfectly: https://stackoverflow.com/a/20198278 As far as I remember, I tried a bunch of methods but none of them was as good as this |
Hi @smttsp! Thanks for the suggestion! I have tried using Canny as an edge detector and further processing its results. It works great, but it is too slow for us. We had to do a tradeoff between speed and the quality of results. The current approach gives good results and runs much faster compared to the Canny detector. |
would you mind sharing your code if you still have it? canny edge detector should not be slow, it is just matrix multiplication. I would be surprised if the code I shared takes more than a few ms. |
I'm sorry I don't have it saved anywhere, could you post some results using your strategy, both from quality and speed perspective. You can start with our example dataset or any of the datasets here |
Some images currently obtain undesirably low blurry quality scores, when they do not appear blurry.
In particular:
Important links
The text was updated successfully, but these errors were encountered: