[Octave-bug-tracker] [bug #51769] [octave forge] (image) imresize bilinear interpolation inaccurate

[Christof Kaufmann]

Follow-up Comment #17, bug #51769 (project octave):

Ah, I just see that I wrote a comment in the tests regarding the difference:

> The floating point error is less than 1e-13, but it affects the rounding
> to int. So a difference of 1 is acceptable.

So, we could check the floating point error. That would require new reference
outputs without uint8, e. g.:
imresize (in, 1.5, 'bilinear', 'Antialiasing', false)

As mentioned, I don't have Matlab installed currently, but I could do that, if
you think floating point comparison is better.

As an alternative, we could find the values near tie break and only accept a
tolerance of 1 for them.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?51769>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/