#7621: usability issues with MIP
---------------------------+------------------------------------------------
Reporter: malb | Owner: jkantor
Type: enhancement | Status: needs_info
Priority: minor | Milestone: sage-4.3
Component: numerical | Keywords:
Work_issues: | Author:
Upstream: N/A | Reviewer:
Merged: |
---------------------------+------------------------------------------------
Changes (by ncohen):
* status: new => needs_info
Comment:
* mipvariables is private because it is just meant to update the
variable's name on the (rare) occasions when the users do nto want to
solve the LP but want to export it to a LP file ( in which case the
variables are expected to "mean" something, and not to be x_1 x_2 x_3
etc...
On which occasion do you think the user may be interested in getting
the list of the variables ? I thought the only important thing was for the
user to have one way to refer to them, but getting a variable "back" would
not tell him what this variable means...
* Well, it is because the user can set variables to a type he chooses
by using p.set_binary or p.set_integer, etc... Do you think they should be
renamed to be public ?
I know there are many ugly parts in this code that needs to be corrected,
and I can not do this alone, as it needs different views to be improved...
Thank you for your help !! :-)
Nathann
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7621#comment:1>
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.
