#18804: LPBackendDictionary - a debugging view of a MIP backend connected to
interactive_simplex_method
-------------------------+-------------------------------------------------
       Reporter:         |        Owner:
  mkoeppe                |       Status:  new
           Type:         |    Milestone:  sage-6.8
  enhancement            |   Resolution:
       Priority:  major  |    Merged in:
      Component:         |    Reviewers:
  numerical              |  Work issues:
       Keywords:  lp     |       Commit:
        Authors:  Aedi   |  440ed874635c88940bc0f06c6ed1e913c29d9042
  Wang                   |     Stopgaps:
Report Upstream:  N/A    |
         Branch:         |
  u/zwang/temp           |
   Dependencies:         |
  #19471, #19472         |
-------------------------+-------------------------------------------------
Changes (by {'newvalue': u'Aedi Wang', 'oldvalue': ''}):

 * commit:   => 440ed874635c88940bc0f06c6ed1e913c29d9042
 * dependencies:   => #19471, #19472
 * author:   => Aedi Wang


Old description:

> This is a follow-up on #18734.
>
> This ticket creates:
>  - a new class, `LPBackendDictionary` (inheriting from
> `LPAbstractDictionary`), would avoid going through `InteractiveLP` and
> rather be tied directly to the MILP backend, using tableau data query
> functions such as `getBInvArow` etc.
> (It would be in a separate file perhaps
> `interactive_backend_dictionary.py`, so as not to add clutter to the
> didactical implementation in `interactive_simplex_method.py`.)
>
> #18732 added most of the missing functions for retrieving the data of the
> dictionary (for the GLPK backend) such as `getBInvARow` etc. (#18763 does
> the same for the COIN backend.)
> #18733 provides a common interface and corresponding
> `MixedIntegerLinearProgram` methods.
>
> Doctests could then test that:
>  - A backend has implemented all the necessary methods to get tableau
> information.
>  - The information is consistent, by checking that the
> `LPBackendDictionary` (in this ticket) and the `LPDictionary` (created in
> #18734) are the same.

New description:

 This is a follow-up on #18734.

 This ticket creates:
  - a new class, `LPBackendDictionary` (inheriting from
 `LPAbstractDictionary`), would avoid going through `InteractiveLP` and
 rather be tied directly to the MILP backend, using tableau data query
 functions such as `getBInvArow` etc.
 (It would be in a separate file perhaps
 `interactive_backend_dictionary.py`, so as not to add clutter to the
 didactical implementation in `interactive_simplex_method.py`.)

 #18732 added most of the missing functions for retrieving the data of the
 dictionary (for the GLPK backend) such as `getBInvARow` etc. The remaining
 functions are provided by #19472.
 #18763 and #19471 do the same for the COIN backend.

 See also: #18733

 Doctests could then test that:
  - A backend has implemented all the necessary methods to get tableau
 information.
  - The information is consistent, by checking that the
 `LPBackendDictionary` (in this ticket) and the `LPDictionary` (created in
 #18734) are the same.

--

Comment:

 New commits:
 
||[http://git.sagemath.org/sage.git/commit/?id=440ed874635c88940bc0f06c6ed1e913c29d9042
 440ed87]||{{{backend dictionaries}}}||

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

Reply via email to