[Octave-bug-tracker] [bug #55059] [octave forge] (image) Failing unit test for grayslice

[Hartmut]

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

I see this:
* With image 2.8.0 release and 2.8.1 release:

>> A = grayslice (uint8([0 100 200 255]), [.1 .4 .5])
A = 0  1  3  3
>> B = grayslice (uint8([0 100 200 255]), [100 199 200 210])
B = 0  0  0  4


* With the current stable branch (only the fixed test from this bug report:
the same as above

* With the current default branch (with Carnes change from comment #6): the
same as above

Those results are different from Carnes in comment #6. What version did you
use?

I have not had access to Matlab to see what their answer is. But thinking
about what the answer should be (following Matlab docs) I would say A= [0 1 3
4] would be good, and B = [0 0 0 0] or [0 0 0 4]. So B might be right, A does
NOT look to be correct. Maybe there is only a +-1 wrong somewhere in our code
for maxint values?

    _______________________________________________________

Reply to this item at:

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

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