[graph-tool] Shortest_distance complexity when used with max_dist

2015-03-06 Thread François
disclaimer I hope this question isn't too dumb, if it is please accept my apologies. /disclaimer Hi list, The graph that I work with has ≈ 30M vertices and ≈ 60M edges. This graph has positive weights, it represents a Road network. I need to compute the shortest path form a node to any other

[graph-tool] Point Lables

2015-03-06 Thread dartdog
I go the initial examples going in an IPython Notebook with no problem, looks great! The SIRS example, and the Price network I'd be happy to post the Gists of them at github. since so many are now using IPython notebooks for analysis. In the examples there are none with hover labels on the

Re: [graph-tool] Shortest_distance complexity when used with max_dist

2015-03-06 Thread Tiago de Paula Peixoto
On 05.03.2015 15:11, François wrote: My question is: What happens when the *max_dist* parameter is specified ? It does not really change the (worst-time) complexity per se, but it should run faster, since the search is stopped sooner. If max_dist is much smaller than typical distances, it can

[graph-tool] Biconnected components and all paths between two vertices of an unoriented multigraph

2015-03-06 Thread atn
Hi, I’m looking for a dll with good documentation that I will call from C#/.Net in order to: 1. generate the biconnected components of an unoriented (multi)graph (i.e. possible loops and parallel edges); 2. generate the list of (simple) paths between two given vertices of an unoriented

Re: [graph-tool] Point Lables

2015-03-06 Thread Tiago de Paula Peixoto
On 06.03.2015 01:20, dartdog wrote: In doing visual exploration it is way helpful to be able to see the properties of a point in a cluster.. The pretty graphs alone are not so helpful? You can place labels on the vertices with the 'vertex_text' parameter: graph_draw(g, vertex_text=labels)

Re: [graph-tool] Shortest_distance complexity when used with max_dist

2015-03-06 Thread François
Tiago Peixoto wrote It does not really change the (worst-time) complexity per se, but it should run faster, since the search is stopped sooner. If max_dist is much smaller than typical distances, it can indeed be much faster. Yes, this situation I deal with. Tiago Peixoto wrote With only