Graphviz Issue Tracker
Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001068graphvizNeatopublic2006-02-27 13:382011-04-28 04:03
ReporterAlex Prinsier 
Assigned Toerg 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSx86-Linux-2.4.27-2-686OS Version
Summary0001068: -v doesn't produce numbers to detect loops
Description



I read in the faq that passing -v would produce some numbers,
and if they kept getting smaller, it wasn't looping, otherwise
it probably was looping. So I tried that, but I'm not seeing any
of those numbers...



This is the output I get:
[[email protected]]output cat "${ID}".dot | twopi -Tjpg -v > test.jpg
The plugin configuration file:
        /usr/local/lib/graphviz/config
                was successfully loaded.
    render : canon cmap cmapx dia dot fig gd gd2 gif hpgl imap ismap jpeg jpg mif mp pcl pic plain plain-ext png ps ps2 svg svgz vrml vtx wbmp xdot
    layout : circo dot fdp neato nop nop1 nop2 twopi
    textlayout :
    device :
    usershape : png-gd
twopi: fontname=Times-Roman fontpath=/usr/share/fonts/type1/gsfonts/n021003l.afm
root = 00D8CD16
Rank separation = 1.000000
Adjusting keyring using scaling



And there it just keeps on going for hours...



Sorry for not having attached a .dot file, but it's really big.
(About 700 nodes to be connected). If you really think it'll be helpful,
I can of course send it ;)



Additional Information

[north] neato and twopi are different programs. twopi -v doesn't print any progress
reports as far as i know


> And there it just keeps on going for hours...
>
>
>
this i'm not sure about but it seems wrong.
twopi is a straightforward algorithm.
e.g. 5 seconds on a graph with 640 nodes, 10,000 edges.

[erg] Following up on Stephen's mail, the output you show is coming from twopi, which
should be very fast. If you are running it and it doesn't finish pretty quickly, that
would seem to indicate a bug. In that case, please email us the input graph, and I'll
modify the Subsystem entry to be twopi.

On the other hand, if it is really neato taking the time, that is not impossible. 700
nodes is not particularly a lot, but it could still take time. For neato, the -v
option should provide an indication of progress.

Please let us know which program is causing the problem and send us the input file.
Thanks.

[aphexer] Here is the input file:
http://aphexer.ulyssis.org/twopi-bug/94C09C7F.dot [^] (536KB)

Excuse me for having misunderstood the faq, I thought the -v option
would also do that for twopi, I was wrong

So it really is twopi I use, not neato, sorry about that

[erg] The actual layout completes fairly quickly. The problem arises because the graph has
set splines=true. Rendering edges as splines is fairly expensive in terms of time,
and your graph has 45420 edges.

There is a related but more fundamental problem with this graph. The complete graph on
684 nodes has 233586 edges, so your graph is pretty close to being complete, even ignoring
the multiedges. Almost any layout of near complete graphs will appear like a black blob.
TagsNo tags attached.
AUXILLARY-FILES
DATE-FIXED
FIX-COMMENT
FORMER-ID890
INPUT-FILEhttp://www.graphviz.org/bugs/b890.dot [^]
OUTPUT-FILE
STATUS-COMMENTFixed
VERSION     2.8
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2011-04-28 04:03 user1 New Issue
2011-04-28 04:03 user1 Assigned To => erg


MantisBT 1.2.5[^]
Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker