[Pkg-octave-devel] Bug#712079: octave-signal: fir1 broken for high order filters
charlie
charlie.hagedorn at gmail.com
Wed Jun 12 19:11:08 UTC 2013
Package: octave-signal
Version: 1.2.2-1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Start octave.
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
octave:1> fir1(10000, [0.01])
error: fir2: grid size must be greater than half the filter order
error: called from:
error: /usr/share/octave/packages/signal-1.2.2/fir2.m at line 89, column 5
error: /usr/share/octave/packages/signal-1.2.2/fir1.m at line 109, column 3
* What outcome did you expect instead?
The generation of a correct finite impulse response filter. This syntax is correct, and has worked for years. This system is updated ~weekly; the bug is probably in the newest update.
This bug appears to be the same as Octave's bug #39177. Second critical-path bug I've seen in 'testing' in more than a decade with Debian. The first was yesterday (hugin). Will revert to previous package.
Thank you!
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages octave-signal depends on:
ii libc6 2.17-3
ii libgcc1 1:4.8.0-7
ii liboctave1 3.6.4-2
ii libstdc++6 4.8.0-7
ii octave 3.6.4-2
ii octave-control 2.4.2-2
ii octave-general 1.3.2-2
ii octave-specfun 1.1.0-1
octave-signal recommends no packages.
octave-signal suggests no packages.
-- no debconf information
More information about the Pkg-octave-devel
mailing list