#18871: MILP formulation for cutwidth
-------------------------+-------------------------------------------------
       Reporter:         |        Owner:
  dcoudert               |       Status:  needs_review
           Type:         |    Milestone:  sage-6.8
  enhancement            |   Resolution:
       Priority:  major  |    Merged in:
      Component:  graph  |    Reviewers:  Nathann Cohen
  theory                 |  Work issues:
       Keywords:         |       Commit:
  cutwidth, MILP         |  d08cffbc663b1733fe4d769fe321d569eefc6e14
        Authors:  David  |     Stopgaps:
  Coudert                |
Report Upstream:  N/A    |
         Branch:         |
  public/18871           |
   Dependencies:         |
-------------------------+-------------------------------------------------

Comment (by dcoudert):

 Hello,

 I agree with your modifications, and I have removed the import of
 MIPSolverException.

 I have a question because the patchbot is complaining about multiline
 doctest:
 {{{
 ========== plugins.doctest_continuation ==========

 --- 6.8.beta8

 +++ 6.8.beta8 + #18871


 -Old-style doctest continuation inserted on 0 non-empty lines
 +inside file:  b/src/sage/graphs/graph_decompositions/cutwidth.pyx
 +@@ -258,6 +312,16 @@ def cutwidth(G, algorithm="exponential", cut_off=0):
 ++        ...       G = graphs.RandomGNP(10, 0.2)
 ++        ...       ve, le = cutwidth.cutwidth_dyn(G)
 ++        ...       vm, lm = cutwidth.cutwidth_MILP(G)
 ++        ...       if ve != vm:
 ++        ...          print "Something goes wrong!"
 +@@ -478,3 +545,157 @@ cdef inline int exists(FastDigraph g, uint8_t *
 neighborhoods, int S, int cost_S
 ++        ...       G = graphs.RandomGNP(10, 0.2)
 ++        ...       ve, le = cutwidth.cutwidth_dyn(G)
 ++        ...       vm, lm = cutwidth.cutwidth_MILP(G)
 ++        ...       if ve != vm:
 ++        ...          print "The solution is not optimal!"
 +Old-style doctest continuation inserted on 10 non-empty lines
 +Traceback (most recent call last):
 +  File "/home/vincent/sage_patchbot/local/bin/patchbot/patchbot.py", line
 906, in test_a_ticket
 +    baseline=baseline, **kwds)
 +  File "/home/vincent/sage_patchbot/local/bin/patchbot/plugins.py", line
 310, in doctest_continuation
 +    msg="Old-style doctest continuation", **kwds)
 +  File "/home/vincent/sage_patchbot/local/bin/patchbot/plugins.py", line
 207, in exclude_new
 +    raise ValueError(full_msg)
 +ValueError: {} inserted on {} non-empty lines
 }}}
 I not sure to understand the problem. Should we use `...` or `....:` as
 indicated here
 http://doc.sagemath.org/html/en/developer/coding_basics.html
 #documentation-strings ?
 Both style are used in the tests of method ` vertex_separation_MILP`, in
 file `vertex_separation.pyx`.
 Let me know what I should do.

 David.

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