[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #62910] [octave forge] (image) bwslect(..., 4)
From: |
Avinoam Kalma |
Subject: |
[Octave-bug-tracker] [bug #62910] [octave forge] (image) bwslect(..., 4) in Octave behaves like bwslect(..., 8) in MATLAB and vice versa |
Date: |
Thu, 18 Aug 2022 01:00:20 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?62910>
Summary: [octave forge] (image) bwslect(...,4) in Octave
behaves like bwslect(...,8) in MATLAB and vice versa
Project: GNU Octave
Submitter: avinoam
Submitted: Thu 18 Aug 2022 05:00:19 AM UTC
Category: Octave Forge Package
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Matlab Compatibility
Status: None
Assigned to: avinoam
Originator Name: Avinoam
Originator Email:
Open/Closed: Open
Release: other
Discussion Lock: Any
Operating System: Any
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Thu 18 Aug 2022 05:00:19 AM UTC By: Avinoam Kalma <avinoam>
Bug#50071 was "[octave forge] (image) bwfill(...,4) in Octave behaves like
bwfill(...,8) in MATLAB and vice versa".
This bug has been fixed.
But bwslect calls bwfill, and this fix was not good for bwslect.
For example, in MATLAB
>> img = [0,1,0;0,1,1;1,0,1]; A = bwselect(~img,1,1,4)
ans =
1 0 0
1 0 0
0 0 0
>> img = [0,1,0;0,1,1;1,0,1]; A = bwselect(~img,1,1,8)
ans =
1 0 0
1 0 0
0 1 0
In Octave the results are the opposite.
I will prepare a patch to fix this
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62910>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #62910] [octave forge] (image) bwslect(..., 4) in Octave behaves like bwslect(..., 8) in MATLAB and vice versa,
Avinoam Kalma <=