-
Notifications
You must be signed in to change notification settings - Fork 4
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
PaDiM Shared Performance #7
Comments
I think it really depends on the kind of images you are dealing with. For texture images where the normal data has a small number of modalities then a shared variant may be good enough. For objects where the location is the patches are very different based on their location on the image then it won't work as well. Doing a quick test on 2 mvtec datasets:
The main advantage being the much smaller memory footprint and not really performance. |
How much did you test |
I won't expect the batch size to have any impact on the performance since batch samples don't interact with each other. What impact do you think it could have ? |
I'll leave it after a test |
How much is the difference in performance compare to original PaDiM?
The text was updated successfully, but these errors were encountered: