#18910: Boost minimum spanning tree
-------------------------------------+-------------------------------------
Reporter: borassi | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.8
Component: graph theory | Resolution:
Keywords: Boost, minimum | Merged in:
spanning tree | Reviewers: David Coudert
Authors: Michele Borassi | Work issues:
Report Upstream: N/A | Commit:
Branch: | 66c6aea291d11529833931cc094abd7b35df794c
u/borassi/boost_minimum_spanning_tree| Stopgaps:
Dependencies: #18876, #18906 |
-------------------------------------+-------------------------------------
Comment (by borassi):
Yes, it is normal, I think: I modified that line only after I merged
#18876. However, I do not think it is a problem, because the new commit in
#18876 should not create conflicts (I have tested the merge).
In any case, I re-merged them with this new commit.
Replying to [comment:22 dcoudert]:
> When I click on the link to the code (to of the page, branch
`u/borassi/boost_minimum_spanning_tree`), for file `bandwidth.pyx` I see
the following line which has been changed in #18876.
> {{{
> +
:meth:`bandwidth_heuristics()<sage.graphs.base.boost_graph.bandwidth_heuristics>`
| Uses Boost heuristics to approximate the bandwidth of the input graph
> }}}
> Is it normal??
--
Ticket URL: <http://trac.sagemath.org/ticket/18910#comment:23>
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.
