qp() in Octave 3.0.0 returns result egregiously violating input constraints

[Joshua Redstone]

Hi John,
I've attached a data file created with (on OSX):
    save -binary -z "./example.dat" x0 H Q A B LB UB A_LB A_IN A_UB

The following should reproduce the problem for you:
   load "example.dat"
   [X, OBJ, INFO, LAMBDA] = qp(x0, H, Q, A, B, LB, UB, A_LB, A_IN, A_UB)

With my qp.m that I modified so the last arguement is maxiter, I get the
follow first few lines of output:
octave-3.0.0:5> [X, OBJ, INFO, LAMBDA] = qp(x0, H, Q, A, B, LB, UB, A_LB,
A_IN, A_UB, 187)
X =

   0.17954
   0.00000
   0.01742
   0.00304
   0.16220
   [... output truncated.... ]

octave-3.0.0:6> [X, OBJ, INFO, LAMBDA] = qp(x0, H, Q, A, B, LB, UB, A_LB,
A_IN, A_UB, 188)
X =

   8.7626e+13
   5.1887e+00
   1.0476e+13
  -9.8103e+13
   2.0382e+15
  -6.1036e+00
   2.3327e+00
   [.... output truncated ....]

I'm not sure how to scale down the problem or generate it with a script as
other datasets of this type don't exhibit this behavior.  The numbers
originate from some empirical data sets.
Let me know if there anything else I can do to help.
Thanks,
Josh

On Fri, Apr 4, 2008 at 1:48 PM, Joshua Redstone <redstone at gmail.com> wrote:

> OK - I"ll get it in that form.  I think I may have lost a race with the
> moderator and so you may see an old email come thru
> with an attachment in a less usefull format.
> Josh
>
>
> On Fri, Apr 4, 2008 at 1:32 PM, John W. Eaton <jwe at bevo.che.wisc.edu>
> wrote:
>
> > On  4-Apr-2008, Joshua Redstone wrote:
> >
> > | Hi Gabriele,
> > | Thanks for your resonse.  The problematic example involves 100
> > variables.
> > | What format would be most convenient for me to send it in?
> > | I've set 'format long g' and printed out all the args to qp() that I
> > use,
> > | naming them as they are named in qp.m, and attached the result
> > | to this email (gzipped).
> >
> > How about in a format that can be read by Octave, along with the
> > command that you use to invoke the qp function?  Make it so that we
> > can do
> >
> >  load somefile.dat
> >  qp (?)
> >
> > where you tell us what ? should be so that we can reproduce the
> > problem.
> >
> > Where do the numbers come from?  Is it possible to generate them with
> > a script?
> >
> > Make it easy for us to reproduce the problem and we are more
> > likely to help debug it...
> >
> > jwe
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.cae.wisc.edu/pipermail/bug-octave/attachments/20080404/7bdc3f5c/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example.dat
Type: application/octet-stream
Size: 82018 bytes
Desc: not available
Url : https://www.cae.wisc.edu/pipermail/bug-octave/attachments/20080404/7bdc3f5c/attachment-0001.obj