#12823: Allow constants for objective function & deletion of rows in
MixedIntegerLinearProgram
--------------------------------------+-------------------------------------
Reporter: john_perry | Owner: ncohen
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: linear programming | Resolution:
Keywords: solver objective | Work issues: failing doctests
Report Upstream: N/A | Reviewers:
Authors: john_perry, ncohen | Merged in:
Dependencies: 12833 | Stopgaps:
--------------------------------------+-------------------------------------
Comment (by john_perry):
Replying to [comment:19 ncohen]:
> Well, I would prefer much more to have only remove_constraint than
remove_constraintS. Otherwise we will be calling remove_constraints([1])
which looks a bit odd.
Amusingly enough, I think `remove_constraint([1,2,3])` looks far more odd
than `remove_constraints([1])`.
> But what about what I just said earlier : remove the S functions from
the backends, and write generic ones directly in generic_backend ? The
code would be sparser, the features still there !?
I'm not quite following what you're saying. Can you be more specific?
> And this get_values thing is more or less a mistake, because for me
"all" variables are indexed dictionaries `:-)`
I don't understand why that makes it a mistake.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12823#comment:21>
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.
