#12736: More solver options for GLPK
--------------------------------------+-------------------------------------
Reporter: john_perry | Owner: ncohen
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.0
Component: linear programming | Resolution:
Keywords: solver parameters | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: #12309 | Stopgaps:
--------------------------------------+-------------------------------------
Comment (by john_perry):
Okay, it looks as if ''' ''I'' ''' had forgotten to test `mip.pyx` this
time! Basically, I had added to `glpk_backend`'s `solve()` method a test
for correctness when the timer runs out. I did this because otherwise
`mip.pyx` thought there was a solution. (I don't remember exactly why.)
For now, I've changed the expected string in the doctest to reflect what
the backend currently has, but another (better?) mofidication would be to
change the backend to test for the precise signal (`GLP_ETMLIM`) and raise
an exception telling the user that time ran out, so the solution will be
invalid.
Which do youprefer?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12736#comment:29>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
