On 12/01/2012 12:54 AM, alepulver wrote: > On 11/30/2012 04:41 PM, Tiago Peixoto [via Main discussion list for the > graph-tool project] wrote: >> But this is correct. Does it really take five hours if you supply pos = >> random_layout() ?! >> > The one that took 6 hours was without supplying "pos". When I supplied a > random one, it took more than 2 hours and I stopped it. > Strangely, unlike the former it uses only one CPU. I believe graph_draw > is taking too long, because random_layout finishes almost immediatly. > > When using your code to filter the largest component it takes 5 minutes, > most of the time processing the layout (as shown with the verbose option > you suggested). > But graph_draw is not wasting time calculating the graph layout when > supplied random positions, I don't know what it could be doing. > > Does it also happen to you: > pos = gt.random_layout(polysemy) > print "here" > gt.graph_draw(polysemy, pos=pos, output='ejercicio_5_gv.png')
This took only about 2 seconds on my machine... I have no idea how it could take two hours. > I've attached a screenshot, which shows unused space in the image. > > I would like to separate nodes as much as possible so that edges are > visible, or strech them to fit the picture at least. There is obviously something wrong with the bounding box calculation. I'll take a look into it. Cheers, Tiago -- Tiago de Paula Peixoto <[email protected]>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ graph-tool mailing list [email protected] http://lists.skewed.de/mailman/listinfo/graph-tool
