#12823: Allow constants for objective function & deletion of rows in
MixedIntegerLinearProgram
--------------------------------------+-------------------------------------
Reporter: john_perry | Owner: ncohen
Type: defect | Status: needs_info
Priority: major | Milestone: sage-5.0
Component: linear programming | Resolution:
Keywords: solver objective | Work issues:
Report Upstream: N/A | Reviewers:
Authors: john_perry, ncohen | Merged in:
Dependencies: | Stopgaps:
--------------------------------------+-------------------------------------
Comment (by john_perry):
Replying to [comment:5 ncohen]:
> Well, there is no need to test functions 10 times in the same way, so
the best is to write real hard tests in the backends, and some tests just
meant as examples for the users in the documentation of numerical/mip.pyx.
Okay. I added a relatively simplex doctest for `mip.pyx` that illustrates
removing constraints in a way that works for both GLPK and Coin. Its
warning clause should hopefully alert the reader to look up the details
for the solver they are using. While I was at it, I also fixed more output
problems in `show()`.
I guess it's time for you to referee this one, and to submit a patch for
the other solvers. `:-)`
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12823#comment:6>
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.
