#12736: More solver options for GLPK
--------------------------------------+-------------------------------------
Reporter: john_perry | Owner: ncohen
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: linear programming | Resolution:
Keywords: solver parameters | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
--------------------------------------+-------------------------------------
Comment (by ncohen):
Helloooooooo John !!
> While working on this tonight, I realized that mip.pyx expects the
`timelimit` parameter for both CPLEX and GLPK to be in seconds. To get
around this, I added a new parameter, `timelimit_intopt` and
`timelimit_simplex`; these accept milliseconds.
Hmmm... Why do you name this parameter timelimit_intopt or
timelimit_simplex and not timelimit_seconds, or something like that ? What
does it specifically have to do with simplex or intopt ? I think it would
be better to have only one parameter for timelimit, and if you think that
milliseconds are better what about having only one parameter which accepts
milliseconds ? By the way, it is already possible to define the timelimit
up to milisecond with this argument. The code actually multiplies the
input by 1000 before updating GLPK's value `:-)`
Nathann
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12736#comment:15>
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.
