#10341: make MIP backend interface more Python-ic
----------------------------------------------+-----------------------------
   Reporter:  malb                            |       Owner:  ncohen    
       Type:  enhancement                     |      Status:  needs_work
   Priority:  major                           |   Milestone:  sage-4.6.2
  Component:  linear programming              |    Keywords:  LP, MIP   
     Author:  Martin Albrecht, Nathann Cohen  |    Upstream:  N/A       
   Reviewer:  Martin Albrecht, Nathann Cohen  |      Merged:            
Work_issues:                                  |  
----------------------------------------------+-----------------------------
Changes (by ncohen):

  * status:  needs_info => needs_work


Old description:

> Sage 4.6.1 will contain a new set of backend classes for mixed integer
> programming, which will make it easier to write interfaces for other
> solvers. There has been some off-list discussion about this interface and
> the follow changes were agreed upon:
>
>  * :func: `add_linear_constraint` should allow ``lb`` and ``ub``  instead
> of direction and one bound, it's more expressive.
>  * :func:`add_variable` should return the index of the newly created
> variable instead of the next index.
>  * change :func:`add_linear_constraint` to accept any iterable of the
> form`` [(c,v) ...]``
>  * ``min`` and ``max`` should be lower bound (or ``lb``) and upper bound
> (or ``ub``) to conform to MIP conventions
>  * allow parameters in :func:`add_variable`
>
> The patches are to be applied in this order:
>
>     * mip_interface_changes.patch
>     * trac_10431-part2.patch
>     * trac_10431-part3.patch
>     * trac_10431-part4.patch

New description:

 Sage 4.6.1 will contain a new set of backend classes for mixed integer
 programming, which will make it easier to write interfaces for other
 solvers. There has been some off-list discussion about this interface and
 the follow changes were agreed upon:

  * :func: `add_linear_constraint` should allow ``lb`` and ``ub``  instead
 of direction and one bound, it's more expressive.
  * :func:`add_variable` should return the index of the newly created
 variable instead of the next index.
  * change :func:`add_linear_constraint` to accept any iterable of the
 form`` [(c,v) ...]``
  * ``min`` and ``max`` should be lower bound (or ``lb``) and upper bound
 (or ``ub``) to conform to MIP conventions
  * allow parameters in :func:`add_variable`

 The patches are to be applied in this order:

     * mip_interface_changes.patch
     * trac_10431-part2.patch
     * trac_10431-part3.patch
     * trac_10431-part4.patch
     * trac_10431-part5.patch

--

Comment:

 It should ! I forgot to update the ticket's description `:-)`

 Nathann

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