#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):

 Hellooooooooo !!!

 > Yeah. The long list of parameters can be a drag, but that's the price of
 enabling everything in GLPK. Alternately, we could decide to take a bunch
 of things off (would people actually use them?) but I'll bet that if we
 remove Gomory cuts, say, then we'll hear something in six weeks. `;-)`

 Oh, I really do not mind, I was just looking at the code and thinking that
 if the user wanted to set the LAST parameter the code would test all
 others first. That's why I would have wanted some dichotomy ! `:-D`
 But that is just a natural reflex. Of course it is muuuuch better
 implemented like that.

 > If your focus is a handful of large linear programs, the penalty of
 Python strings v. machine integers might not matter. If your focus is a
 few thousand small linear programs, it could be an issue -- especially if
 you start mucking around w/options quite a bit.
 >
 > Admittedly, in my own work I don't seem to need the options after all,
 and I've managed to revise, revise, revise my approach until I'm now
 creating only a few tens of programs, instead of a few thousand. So it's
 not that big an issue for me as it used to be. But it could become an
 issue again in the future.

 Well, I was just surprised that comparing integers was *that much shorter*
 than comparing strings. And that it could become the bottleneck in LP
 codes `:-)`

 Ok, I should give this code a proper review now !

 Nathann

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12736#comment:20>
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.

Reply via email to