[Top][All Lists]

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

[Octave-bug-tracker] [bug #55059] [octave forge] (image) Failing unit te

From: Carnë Draug
Subject: [Octave-bug-tracker] [bug #55059] [octave forge] (image) Failing unit test for grayslice
Date: Sat, 1 Dec 2018 08:47:05 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #8, bug #55059 (project octave):


The minimal example I showed on comment #6 are the Matlab results (sorry, I
should have been more clear).  It shows we are Matlab incompatible for images
of non uint8 type (and possibly other integer types).

The thing is that I'm not sure how to get Matlab compatible results. It seems
to me that to be Matlab compatible, the second argument (V) needs to be on the
same range as the data type of the image. But Matlab documentation
specifically documents that values should be in the range [0 1]

>From Matlab documentation:
> Note that the threshold values are always between 0 and 1, even if I is of
class uint8 or uint16. In this case, each threshold value is multiplied by 255
or 65535 to determine the actual threshold to use.

It's not uncommon for Matlab to be wrong, but this is way too wrong which is
why I'm thinking that maybe I'm missing something.


Reply to this item at:


  Message sent via Savannah

reply via email to

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