[Octave-bug-tracker] [bug #50153] image package: bwperim result on 1x1input incorrect

[Hartmut]

URL:
  <http://savannah.gnu.org/bugs/?50153>

                 Summary: image package: bwperim result on 1x1input incorrect
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Thu 26 Jan 2017 12:50:57 PM GMT
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.0
        Operating System: Any

    _______________________________________________________

Details:

This happens with Octave 4.2.0 and the current image-2.6.1.

The result of this little script

BW = true;
P = bwperim(BW)
Q = bwperim(BW, 8)


returns twice a single 0 in Octave, but it returns twice a 1 in Matlab. The
Matlab result makes more sense to me, since even a 1x1 region DOES have a
perimeter, which is the pixel itself.

(I hit this when implementing a new feature for regionprops. But I will
probably work around this bwperim issue in regionprops, to not create too many
inter-dependencies of patches.)






    _______________________________________________________

Reply to this item at:

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

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