[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #60492] [octave forge] (signal) error in clust
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #60492] [octave forge] (signal) error in clustersegment with input not strictly 0s and 1s |
Date: |
Sat, 1 May 2021 16:23:08 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36 |
Update of bug #60492 (project octave):
Severity: 3 - Normal => 2 - Minor
Priority: 5 - Normal => 3 - Low
Status: None => Confirmed
Release: 5.2.0 => dev
Summary: [octave forge] (signal) error in clustersegment =>
[octave forge] (signal) error in clustersegment with input not strictly 0s and
1s
_______________________________________________________
Follow-up Comment #1:
Agree, this function could be a little friendlier if the input data is not in
the exact form that is expected.
Note that the docs say that the input vector is expected to be entirely ones
and zeros. So if you try this instead, you get the expected result:
>> clustersegment (logical (x))
ans =
2
4
I would accept patches to make this function automatically convert the input
into the expected ones and zeros, using 'logical()' or '!= 0' or '!!', any of
these are probably equally efficient.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60492>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/