3 ms·
Here's a first cut implementation in ruby. Requires the "hpricot" gem. Outputs a dot file to stdout. http://gist.github.com/35841 http://gist.github.com/35841
by jey 18y ago
Here's a first cut implementation in ruby. Requires the "hpricot" gem. Outputs a dot file to stdout. http://gist.github.com/35841 http://gist.github.com/35841
Output from the above is at: http://jey.kottalam.net/tmp/obgraph.out http://jey.kottalam.net/tmp/obgraph.out
I tried rendering this with "dot -Tcmapx -oob.map -Tgif -oob.gif" but dot segfaulted after 70 minutes. The code as posted at gist only outputs nodes for articles written by Eliezer in an attempt to make the dot file a manageable size. Tips/fixes appreciated.
- jjs 18y agoNot sure if it will work, but try: 1) Rendering an undirected graph via graphviz's neato tool. 2) Rendering to svg, which might let graphviz not have to keep as much rendering information in memory at any one time. 3) Asking about it on the grapviz-interest mailing list. https://mailman.research.att.com/mailman/listinfo/graphviz-interest https://mailman.research.att.com/mailman/listinfo/graphviz-i...
- Eliezer 18y agoYeah, it's that thing with the segfault that I worried about. "Highly interconnected." Thanks for the graph, which I may be able to use for my own purposes even if I can't show it. There's got to be standard graphing tools for things that are highly connected...
- khafra 18y agoWhen Daniel J. Bernstein made his DAGs of standard crypto algorithms (http://cr.yp.to/cipherdag/cipherdag-20070630.pdf http://cr.yp.to/cipherdag/cipherdag-20070630.pdf) he mentioned that they'd crashed every standard drawing tool he tried. He makes a reference to "...my own drawing tools, which are much more careful in their use of memory." Unfortunately, I'm not sure where to obtain DJB's drawing tools.