[Octave-bug-tracker] [bug #60946] [octave forge] (image) bug in imresize implementation

[Hartmut]

Follow-up Comment #3, bug #60946 (project octave):

I had a look into this.

It turned out that the behavior described in the original bug report is
already fixed with our current version of imresize.m in the image repo. @Rick:
Sorry for not releasing this new version sooner. It will be part of the next
release of the image package.

Nevertheless, I also checked resizing "1 pixel rgb images" with other
interpolation methods, instead of "nearest", and those ones did not yet work
properly because of the mechanics inside of our (Octave only) imremap.m. (This
also wrong behavior might be what Rick said in comment #1).

Matlab can deal well with resizing 1 pixel rgb images, using any interpolation
method in imresize.

As a result I
* changed the code in imremap.m such that those 1 pixel rgb images now work
properly, also with other interpolation methods than "nearest", by introducing
a separate code path for those types of images.
* I added a BIST to imresize.m to check this behavior with two different
interpolation methods.

I will attach a patch file (V1). Please give me feedback during the next few
weeks. Afterwards I would like to push this patch to the image repository.



(file #51686)
    _______________________________________________________

Additional Item Attachment:

File name: imresize_1px_V1.patch          Size:1 KB
    <https://file.savannah.gnu.org/file/imresize_1px_V1.patch?file_id=51686>



    _______________________________________________________

Reply to this item at:

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

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