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

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

[Octave-bug-tracker] [bug #56170] [octave forge] (signal) results from f


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #56170] [octave forge] (signal) results from fir1 differ from Matlab (inaccurate?)
Date: Fri, 19 Apr 2019 11:41:45 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36

Update of bug #56170 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

Octave's fir1 is currently based on fir2. It converts its arguments into fir2
arguments and normalizes the result.

Maybe we should compare Octave's fir2 against Matlab for these examples and
see if that is the underlying problem.

Or maybe the "FIXME: Consider using exact expression (in terms of sinc) for
the impulse response rather than relying on fir2" needs to be looked at.

The equivalent calls to fir2 are


fir2 (2048, [0, 100/(48000/2), 100/(48000/2), 1], [1, 1, 0, 0], [], 2, [])
fir2 (2048, [0, 100/48000/2, 100/48000/2, 1], [1, 1, 0, 0], [], 2, [])


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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