Re: [Doxygen-users] how to avoid running dot for really big diagrams

[Oliver S. <oli...@ut...>]

----- Original Message -----
From: "Dimitri van Heesch" <di...@st...>
To: <dox...@li...>
Sent: Saturday, March 29, 2003 9:09 AM
Subject: Re: [Doxygen-users] how to avoid running dot for really big
diagrams


> will give better results. Maybe a better way to reduce time is to add an
> config option to limit the graph depth (i.e. distance from the root) or
> maximum node count, then that could be used as the upper bound for
searching
> a best fit. Let me know which one (graph depth or node count) you think is
> better.


Forgot to answer the last question: personally, I find that node count would
be hard to judge. I could have a trivial graph of depth 1 (ie two levels)
with 20 nodes on the second level, if my limit is 18 nodes, which two get
clipped?

Depth is fairly intuitive and also is related to hierarchical complexity
(each extra depth "typically" has exponentially more info than the level
below).

That said, you could deal with this issue by adding two \commands, e.g.
\dot_max_graph_depth and \dot_max_node_count that the user could specify in
the class doc block to change from the default config options
DOT_MAX_GRAPH_DEPTH (default infinite, >=1) and DOT_MAX_NODE_COUNT (default
infinite, >= 1). But as I mentioned in my last email on this thread, a
simple test might be better before going into such details.

JM2CW.
Oliver