[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #45332] Upsample in signal package, not contro
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #45332] Upsample in signal package, not control |
Date: |
Tue, 16 Jun 2015 18:37:10 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Firefox/38.0 |
Update of bug #45332 (project octave):
Category: Octave Forge Package => Octave Function
Severity: 3 - Normal => 2 - Minor
Priority: 5 - Normal => 3 - Low
Status: None => Confirmed
Release: 4.0.0 => dev
_______________________________________________________
Follow-up Comment #4:
Right, the point is that the one in the signal package is a "bare" function
that operates on vectors, and the placeholder for the one in the control
package would operate on control system classes (either @lti/upsample.m or
@tf/upsample.m). But the missing function hook in Octave only matches against
the simple function name, it has no idea whether it should be an ordinary
function or a class method or a class constructor, etc.
There are lots of duplicates in the __unimplemented__.m function file now that
I am looking for them. Functions like get, set, log, size probably don't need
to be listed there. Upsample shows up in both control and signal. Step shows
up in both control and statistics. The statistics section actually has a lot
of self-duplicates, e.g. "predict" is listed 8 times in a row.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45332>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/