[Octave-bug-tracker] [bug #51264] imread incorrect results (vs python matlab results)

[Nicholas Jankowski]

Follow-up Comment #5, bug #51264 (project octave):

adding in a bit of matlab compatibility commentary, where this does seem to be
an issue:

running the comment #4 commands and then loading the two images in Matlab
2017a:

x1 = randn (100, 100);
imwrite (x1, 'foo1.jpg');
x2 = repmat (x1, 1, 1, 3);
imwrite (x2, 'foo2.jpg');
foo1 = imread('foo1.jpg');
foo2 = imread('foo2.jpg');
whos
  Name        Size                Bytes  Class     Attributes

  foo1      100x100               10000  uint8               
  foo2      100x100x3             30000  uint8               
  x1        100x100               80000  double              
  x2        100x100x3            240000  double              



Then in Octave 4.2.1 on Windows 7 64bit:


>> whos
Variables in the current scope:

   Attr Name        Size                     Bytes  Class
   ==== ====        ====                     =====  =====
        foo1      100x100                    10000  uint8
        foo2      100x100                    10000  uint8
        x1        100x100                    80000  double
        x2        100x100x3                 240000  double

Total is 60000 elements using 340000 bytes




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51264>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/