[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #63560] [octave forge] (image) imresize gives

From: Raghavan
Subject: [Octave-bug-tracker] [bug #63560] [octave forge] (image) imresize gives inaccurate result
Date: Sun, 22 Jan 2023 11:48:01 -0500 (EST)

Follow-up Comment #4, bug #63560 (project octave):

I verified that the problem is not visible by setting "antialiasing" as false.
 I was not able to compare pixel values numerically with an earlier version
since this option is not available in a previous version (octave:6.4.0,

Since antialiasing is used only when down-sizing, I tried resizing to
[200,200] (up-sizing) instead of [100,100].  The stripe artifact was not seen
in both the older and newer (octave: 7.3.0, image: 2.14.0) versions.
In 7.3.0, I also verified that for [200,200] output size, the output was the
same with and without setting the "antialiasing" option as false.  This is as

One note however: While no visual difference was found between outputs for
6.4.0 and 7.3.0 for output size [200,200], there was a difference of up to 33
in pixel values when I took an image difference.  This may or may not be
another problem with bilinear interpolation.

Overall, I would agree that the original problem that I reported is due to a
bug in anti-aliasing, which seems to be reported already.


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]