SSIM not working for negative numbers
See original GitHub issueHi!
SSIM module isn’t accepting negative numbers, as well as numbers greater than 1. This isn’t an issue when working with photographic data, but when working with numerical data it’s a hindrance. E.g.from skimage.metrics import structural_similarity
handles negative numbers well. Could you please implement this? Or is it enough for me to edit the lines in ssim.py
?
Cheers!
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
The interpretation of scikit-image SSIM (structural similarity ...
In the Skimage SSIM source code, Covarience of the two images is represented by vxy, and it can be negative in some cases....
Read more >On the proper use of structural similarity for the robust ...
Notably, SSIM is designed to work on a strictly positive intensity scale, which is generally not the case in medical imaging. Common intensity...
Read more >All about Structural Similarity Index (SSIM): Theory + Code ...
SSIM is used as a metric to measure the similarity between two given ... Just click on the “Open in Colab” link to...
Read more >Structural similarity (SSIM) index for measuring image quality
This MATLAB function calculates the structural similarity (SSIM) index for grayscale image or volume A using ref as the reference image or volume....
Read more >On the proper use of structural similarity for the robust ...
Notably, SSIM is designed to work on a strictly positive intensity scale, which is generally not the case in medical imaging. Common intensity ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you very much for clarifying!
I’m not sure what you mean by “not fixed for each batch of images”. When i said your numerical inputs range in
[a,b]
, I meant that a and b are the absolute minimum and maximum values of all the inputs in the dataset, not in a batch. So they should not change “during training”.