Re: Octave Control package bug ?
"Dmitri A. Sergatskov" <[email protected]>
| Newsgroups | gmane.comp.gnu.octave.general |
|---|---|
| Message-ID | <CAO+XyQKFGVsjSffh5RzqksRywKdXkgRNSdo_rM7i+cGxHj0viw@mail.gmail.com> |
On Thu, Sep 17, 2020 at 2:37 AM Andreas Weber <[email protected]> wrote: > Am 16.09.20 um 21:03 schrieb Dmitri A. Sergatskov: > > ... > > I see that there are three different __zero__: > > control-3.2.0/@frd/__zero__.m > > control-3.2.0/@ss/__zero__.m > > control-3.2.0/@tf/__zero__.m > > Can you share the output from > $ find control-3.2.0/ -name "*zero*" > > on my install: > > control-3.2.0/@ss/__zero__.m > control-3.2.0/@frd/__zero__.m > control-3.2.0/@tf/__zero__.m > control-3.2.0/@lti/zero.m > control-3.2.0/__remove_trailing_zeros__.m > control-3.2.0/@tfpoly/__remove_leading_zeros__.m > control-3.2.0/@tfpoly/is_zero.m > control-3.2.0/tfpolyzeros.m > > Is it possible that you have another zero function lingering around from > an older control version? > find control-3.2.0/ -name "*zero*" control-3.2.0/@frd/__zero__.m control-3.2.0/__remove_trailing_zeros__.m control-3.2.0/@ss/__zero__.m control-3.2.0/tfpolyzeros.m control-3.2.0/@tf/__zero__.m control-3.2.0/@lti/zero.m control-3.2.0/@tfpoly/__remove_leading_zeros__.m control-3.2.0/@tfpoly/is_zero.m > > -- Andy > Dmitri. --