#19227: Graphs: DFS and broken distance-parameter
-------------------------------------+-------------------------------------
       Reporter:  jmantysalo         |        Owner:
           Type:  defect             |       Status:  needs_work
       Priority:  major              |    Milestone:  sage-6.9
      Component:  graph theory       |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Jori Mäntysalo     |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/jmantysalo/graphs__dfs_and_broken_distance_parameter|  
89b7490bec7e28f1c63bb81603eeab69fefb4e65
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------
Changes (by {'newvalue': u'Jori M\xe4ntysalo', 'oldvalue': ''}):

 * status:  needs_review => needs_work
 * author:   => Jori Mäntysalo


Old description:

> This bug is visible at least on normal 64-bit Linux machine running self-
> compiled Sage. Might be architechture-dependent.
>
> {{{
> G = DiGraph({1:[2,10],2:[3],3:[4],4:[5],5:[6],10:[4]})
> list(G.depth_first_search(1, distance=3))
> }}}
>
> This should output also `5` as it is three jumps from 1: `1->10->4->5`.
> It is not outputted because `4` is already marked as seen vertex for
> `1->2->3->4`.

New description:

 This bug is visible at least on normal 64-bit Linux machine running self-
 compiled Sage. This is architechture-dependent if you have for example
 both integers and strings as vertices.

 {{{
 G = DiGraph({1:[2,10],2:[3],3:[4],4:[5],5:[6],10:[4]})
 list(G.depth_first_search(1, distance=3))
 }}}

 This could output also `5` as it is three jumps from 1: `1->10->4->5`. It
 is not outputted because `4` is already marked as seen vertex for
 `1->2->3->4`.

--

Comment:

 I can make a better example later, when I am on faster computer.

 But is plain path a good example? It won't show any difference between
 `depth_first_search()` and `breadth_first_search()`.

 Of course you can also do this; we can cross-review our codes.

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