I'll pull together the code from the tests I'm doing, but it will take me a couple of days to get the appropriate releases through work. What would be the best way for me to get it to you? Just email you a tarball of it all? Thanks, Cem Karan On Apr 11, 2013, at 10:54 AM, Tiago de Paula Peixoto wrote:
On 04/11/2013 03:00 AM, CFK wrote:
To test out how well this works, I'm randomly generating graphs and occupied vertices, and then running my code on those randomly generated graphs. Sometimes I'll end up with 50-60 tests successfully completed, and sometimes it'll die on the first test. I have no idea when or how it will die, and when I've set up code to draw the graph immediately prior to calling either dijkstra or astar, the graphs don't look particularly strange, nor do they have anything in common with one another. It just dies with a "RuntimeError: maximum recursion depth exceeded" exception as shown below.
Looks very strange. Could you please provide a minimal self-contained example which triggers the problem?
I'm also getting the divide by zero errors that cairo is complaining about, but I'm less worried about those as they are just part of my debugging display code. In the worst case, I can find a way of displaying everything using some other method.
See if the vertex positions values are strange. Again, a minimal example would allow me to understand the source of the problem.
Cheers, Tiago
-- Tiago de Paula Peixoto <tiago@skewed.de>
_______________________________________________ graph-tool mailing list graph-tool@skewed.de http://lists.skewed.de/mailman/listinfo/graph-tool