[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51936] [octave forge] (signal) zp2sos wrong r
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #51936] [octave forge] (signal) zp2sos wrong results for single zero |
Date: |
Mon, 4 Sep 2017 12:52:51 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Update of bug #51936 (project octave):
Severity: 3 - Normal => 2 - Minor
Status: None => Need Info
Summary: zp2sos wrong results for single zero => [octave
forge] (signal) zp2sos wrong results for single zero
_______________________________________________________
Follow-up Comment #1:
Well let's look at the inverse operation:
[z, p, k] = sos2zp ([1 -1 0 1 0 -1])
z =
1
0
p =
-1
1
k = 1
This matches your third line. This implies that the zeros array may have been
padded.
And if you look into zp2sos.m, if the number of real zeros is not even, the z
array is padded by a single 0. This makes the first the same as the third.
What does Matlab do with these examples? What do you think the results should
be?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51936>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/