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
Hi
This code contains the same error as skimage, and pytorch-ssim you can read full description here: scikit-image/scikit-image#5192
Shortly, when used for estimation of perceptual quality, authors of original paper proposed to downsample images first to make SSIM focus on major differences between reference and distorted inputs.
So what?
If you are using this implementation as a loss function for CNN, you're likely leading it in the wrong direction.
According to Tensorflow's official SSIM code https://www.tensorflow.org/api_docs/python/tf/image/ssim, there isn't the average pooling when image size > 256. So I wonder whether the SSIM proposed here https://github.com/photosynthesis-team/piq should be adopted especially when using SSIM as a metric.
@lijx10
Implementation in PIQ is identical to TF with 1e-4 with flag ‘downsample=False’. Image quality assessment metrics are evaluated not on basis of similarity to TensorFlow code, but on basis of prediction quality and correlation with human judgments.
So the issue with TF is that it poorly measures “perceptual distance” between 2 images and thus it’s better not to use it as a guidance for model optimisation or model selection.
Hi
This code contains the same error as
skimage
, andpytorch-ssim
you can read full description here: scikit-image/scikit-image#5192Shortly, when used for estimation of perceptual quality, authors of original paper proposed to downsample images first to make SSIM focus on major differences between reference and distorted inputs.
So what?
If you are using this implementation as a loss function for CNN, you're likely leading it in the wrong direction.
Alternatives
You can find correct implementation of SSIM, MS-SSIM and some other metrics here:
https://github.com/photosynthesis-team/piq
The text was updated successfully, but these errors were encountered: