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

[Ben Abbott]

On Apr 6, 2008, at 4:41 PM, Gabriele Pannocchia wrote:
>> It appears to work for me.
>>
>> octave:44> INFO
>> INFO =
>> {
>>   solveiter =  200
>>   info =  3
>> }
>>
>> octave:45> OBJ
>> OBJ =  2.5372e-06
>> octave:46>
>
> Do you also know if the starting point computed by glpk (if you do not
> supply the starting point I sent) is feasible or not?

oppps ... sorry, I have no idea how to determine that. How might that  
be done?

btw, I modified line 414 of __qr__.cc to be

-		      if (tmp < 0.0)
+		      if (tmp < -1e-12)

then rebuilt and ran Josh's example, which still fails ... so much for  
shooting into the darkness ;-)

Ben