[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: zp2sos error: cplxpair: could not pair all complex numbers
From: |
Nicholas Jankowski |
Subject: |
Re: zp2sos error: cplxpair: could not pair all complex numbers |
Date: |
Fri, 6 Jan 2017 05:38:49 -0500 |
On Jan 6, 2017 3:20 AM, "hale812" <address@hidden> wrote:
>
> I would like to start the bug ticket again, but as I told it, I have no
> access to bug tracking yet. (I've sent a request)
Everyone has access to the bug tracker.
http://bugs.octave.org
Anyone can submit a bug report. A login account is optional. Give it a try. Along the top right of the page there's a Bugs menu with Submit New as an option. Fill in what you're able and the process starts.
Also, this is a hard stop error that has so far been brought up 2x in 5 years. It also is in a package, not core octave. This may seem critical to you, but if it was a roadblock to more people odds are that it would have been heard about more often.
Nick j.
- Re: zp2sos error: cplxpair: could not pair all complex numbers, (continued)
- Re: zp2sos error: cplxpair: could not pair all complex numbers, Ozzy Lash, 2017/01/05
- Re: zp2sos error: cplxpair: could not pair all complex numbers, Ozzy Lash, 2017/01/05
- Re: zp2sos error: cplxpair: could not pair all complex numbers, hale812, 2017/01/06
- Re: zp2sos error: cplxpair: could not pair all complex numbers, Nicholas Jankowski, 2017/01/06
- Re: zp2sos error: cplxpair: could not pair all complex numbers, Nicholas Jankowski, 2017/01/06
- Re: zp2sos error: cplxpair: could not pair all complex numbers, Ozzy Lash, 2017/01/06
Re: zp2sos error: cplxpair: could not pair all complex numbers, John W. Eaton, 2017/01/05
Re: zp2sos error: cplxpair: could not pair all complex numbers, Nicholas Jankowski, 2017/01/05