#12884: Fix problems introduced by remove_constraint functionality in MIP
----------------------------------------------------------------------------+
Reporter: john_perry |
Owner: ncohen
Type: defect |
Status: needs_review
Priority: minor |
Milestone: sage-5.1
Component: linear programming |
Resolution:
Keywords: glpk, mixed integer programming, mip, linear programming |
Work issues:
Report Upstream: N/A |
Reviewers:
Authors: John Perry |
Merged in:
Dependencies: #12823 |
Stopgaps:
----------------------------------------------------------------------------+
Comment (by john_perry):
> Well, what about taking the ith constraint, then normalize it (as you do
before adding it to the set), then pop the normalized constraint out of
the set ? We could have a _normalize_constraint method in the main class,
which would be called before adding or removing a constraint, couldn't we
?
I thought about that, but would floating-point comparisons be a problem?
> And could you please add a doctest ? Otherwise I am pretty sure we could
forget again this duplication mechanism next time we work on constraints
`:-)`
We already have a doctest for the duplication mechanism. But, sure, I can
add a doctest for this.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12884#comment:3>
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.
