[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #45834] [octave forge] (signal) grpdelay with
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #45834] [octave forge] (signal) grpdelay with a vector of frequencies is not correct |
Date: |
Tue, 3 Apr 2018 14:42:21 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 |
Update of bug #45834 (project octave):
Summary: [octave forge] (signal) [T,wr]=grpdelay(b,a,w) does
not use or return w => [octave forge] (signal) grpdelay with a vector of
frequencies is not correct
_______________________________________________________
Follow-up Comment #2:
After looking at this again, the entire approach that grpdelay currently uses
requires that the frequency points be equally spaced. If the function is
called with an array of frequencies in Hz or radians, only the length of the
array is used to determine at which points to evaluate the delay.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45834>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #45834] [octave forge] (signal) grpdelay with a vector of frequencies is not correct,
Mike Miller <=