[Octave-bug-tracker] [bug #66010] Function glpk produces incorrect output

[anonymous]

Follow-up Comment #7, bug #66010 (group octave):

The previous comment was very useful for me. A bit of data cleansing seems to
solve my problems.

This is surprising to me. Even without data cleansing the problem has a
solution, as far as I can see, or if it hadn't I would have expected an error
message (10. no primal feasible solution). I still don't fully understand how
small rounding errors can have the effect they have. (Apparently I am even
less of an expert on linear programming.) But I am happy that I can now use
glpk.

A small side comment: if param.lpsolver = 2, then setting param.msglev = 1
does not have the desired effect (error messages only). If one uses glpk in a
loop (as I do) this means a lot of annoying messages flooding the screen. But
this is a minor issue and I can anyway now work with the default value
param.lpsolver = 1.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66010>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc
Description: PGP signature