octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60597] [octave forge] (signal) Bug in functio


From: Charles Praplan
Subject: [Octave-bug-tracker] [bug #60597] [octave forge] (signal) Bug in functions handling SOS
Date: Fri, 14 May 2021 08:24:43 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0

Follow-up Comment #3, bug #60597 (project octave):

No problem, I will continue editing the functions and post a new bug report
for cplxreal.

Now about the Matlab compatibility :

Return values :
---------------
I'm pretty sure that these functions return correct results what is not the
case of Matlab. See following example for which Matlab returs an incorrect
value for A2:
B0=[1 0 0 1], A0=[1 1 1], sys=tf(B0, A0), [B1,A1]=tfdata(sys,'vector'),
sos=tf2sos(B0,A0), [B2,A2]=sos2tf(sos)

Input arguments :
---------------
If it is clear that zp2sos must combine complex-conjugate poles or zeros, what
to do with real poles or zeros?
My idea was to let the user decide, therefore the additional parameter for
zp2sos . Now if Matlab compatibility is more important, we have to decide.
Perhaps not combining real values is preferable (so that it is clear, seeing
the result, that the poles or zeros are real). However the case of having
multiple real zeros or poles is less frequent, so not very important.

Which solution do you prefer?



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60597>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]