-
Notifications
You must be signed in to change notification settings - Fork 672
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
[Bug]: Output segmentation mask mismatch #1660
Comments
Hi, thanks for reporting this. It looks very similar to #1447 so I think there is actually a problem with center cropping. anomalib/src/anomalib/post_processing/visualizer.py Lines 102 to 103 in 9effa29
I belive this needs to be handled differently. Either we also pass center crop data to visualizer, or we pass the normalization data to de-normalize the image. anomalib/anomalib/post_processing/visualizer.py Lines 77 to 78 in 4860abc
@samet-akcay do you maybe remember why that was the case and what should be done in this case since visualizing with center-crop seems to be an issue? |
Yeah, I think it was to avoid denormalization if i remember correctly, @djdameln? @ashwinvaidya17 is currently working on #1530. Maybe we could consider addressing it there, or a separate one? |
Hi, I would like to work on this issue. |
Sure 😊, thanks. |
Thanks @Akash-Chokhani ! |
Please keep an eye on this PR #1706 as it might cause some conflicts to your work. We plan to merge it by tomorrow |
Got it. Thanks for letting me know. |
@ashwinvaidya17 @samet-akcay How is this solved? |
Describe the bug
Hello, I have recently found that in the output images the subplots of image/predicted heatmap and groundtruth/predicted mask/segmentation result does not match, see the following image:
I am pretty sure it was caused by the centercrop operation. After disabling the parameter the results looks reasonable:
Dataset
N/A
Model
N/A
Steps to reproduce the behavior
None
OS information
Not relevant
Expected behavior
None
Screenshots
No response
Pip/GitHub
GitHub
What version/branch did you use?
No response
Configuration YAML
Not relevant
Logs
Code of Conduct
The text was updated successfully, but these errors were encountered: