#16504: A mandatory 'nonnegative' argument for
MixedIntegerLinearProgram.new_variable() until the standard changes
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: linear | Resolution:
programming | Merged in:
Keywords: | Reviewers:
Authors: Nathann Cohen | Work issues:
Report Upstream: N/A | Commit:
Branch: u/ncohen/16504 | b1f43af754d4ab7e136015519c7fc0cdbe32dd36
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by {'newvalue': u'Nathann Cohen', 'oldvalue': ''}):
* author: => Nathann Cohen
Comment:
Replying to [comment:18 dimpase]:
> As now `p.set_min(v,17)` becomes possible, why not have optional `max`
and `min` in `new_variable()` (many solvers have it, at least per
variable) ? E.g. `v=p.new_variable(min=17, max=18)`. A usual application
is relaxation of binary IPs, so one would have real variables
`p.new_variable(min=0, max=1)`.
I agree, but perhaps not on this ticket. Let's try not to do too many
things at the same time.
--
Ticket URL: <http://trac.sagemath.org/ticket/16504#comment:19>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
