You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All of the above (and potentially some other models, but I think those are the only four) should have normalization set to just get all the images to [0, 1] range.
Screenshots
No response
Pip/GitHub
GitHub
What version/branch did you use?
main
Configuration YAML
/
Logs
/
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Does using imagenet normalization affect the results much? Did you do any experiments? When I used draem, the anomaly maps rendered poorly. The anomalous regions are not rendered red. I'm still trying to figure out why.
Describe the bug
Some of the models have wrong normalization setup in current version of code.
This list includes: DSR, DRAEM, EfficientAD, and rkde.
All of the above methods shouldn't use imagenet normalization, but they have the default method setup (which uses imagenet normaliztion):
anomalib/src/anomalib/models/components/base/anomaly_module.py
Lines 224 to 241 in 9482d34
or in case of the EfficientAD it is manually set to imagenet:
anomalib/src/anomalib/models/image/efficient_ad/lightning_model.py
Lines 311 to 319 in 9482d34
Dataset
Other (please specify in the text field below)
Model
Other (please specify in the field below)
Steps to reproduce the behavior
/
OS information
/
Expected behavior
All of the above (and potentially some other models, but I think those are the only four) should have normalization set to just get all the images to [0, 1] range.
Screenshots
No response
Pip/GitHub
GitHub
What version/branch did you use?
main
Configuration YAML
/
Logs
Code of Conduct
The text was updated successfully, but these errors were encountered: