[Octave-bug-tracker] [bug #46390] image package - im2bw interprets threshold slightly different than Matlab

[Avinoam Kalma]

Follow-up Comment #9, bug #46390 (project octave):

Thanks for fixing the cset. Please push the attached cset,
but remove me from the copyright line. Thanks :-) 

Next week I hope to add more tests.

Just a question: I have compare to execution times for this
version and for version with


thres = (thres * I_range) + I_min
 

i.e. leaving the thresh in double, without changing image type.
using the following script


I = uint8([0:255]);

S = 0;
for i=0:10000
    bw = im2bw(I, i/100000);
    s = sum(bw);
    S = S+s;
end
 

I got the same results but 20% faster.
Any reason for doing the cast & floor

    _______________________________________________________

Reply to this item at:

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

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