Projects tagged ‘graphviz’ and ‘visualization’

phpCallGraph is a tool to generate static call graphs for PHP source code. Such a graph visualizes the call dependencies among methods or functions of an application. Arrows represent calls from one ... [More] method to another method. Classes are drawn as rectangles containing the respective methods. The graphs can be leveraged to gain a better understanding of large PHP applications or even to debunk design flaws in them. The core of the call graph generator forms an object-oriented PHP5 library, which may also be integrated in other projects. It leverages the InstantSVC CodeAnalyzer and DOT. On top of it, a commandline application allows easy creation of call graphs in various formats, e.g. text, png, jpg or svg. phpCallGraph is free software licensed under GPLv3. [Less]

pycallgraph is a Python library that creates call graphs for Python programs.

This is the homepage of pydot, a Python interface to Graphviz's Dot language. pydot allows to easily create both directed and non directed graphs from Python. Currently all attributes implemented in ... [More] the Dot language are supported (up to Graphviz 2.16). Output can be inlined in Postscript into interactive scientific environments like TeXmacs, or output in any of the format's supported by the Graphviz tools dot, neato, twopi. Requirementspyparsing in order to load DOT files. Graphviz to render the graphs. ChangelogThe release 1.0.2 of pydot boasts the following: The parser has been improved a lot. It passes all of GraphViz's regression tests (which I consider quite an accomplishment seeing the kind of crazy constructs on those ) Different charsets should now be dealt with properly. The search of GraphViz's executables has been improved for all platforms. On Windows, paths and registry keys are searched. On Unix now it should exhibit the same behavior as the traditional shell path search. (Thanks Andy Gimblett and many others) Double-quoted paths in Windows are nor properly handled. The os.path.exists() check fails if a valid path is enclosed within quotes. 'type' keyword has been changed everywhere to 'graph_type' Better handling of Node/Edge/Graph defaults. Added methods: set_graph_defaults, set_node_defaults, set_edge_defaults, get_graph_defaults, get_node_defaults, get_edge_defaults Now it's possible to use rank to lay out nodes at the same level graph = pydot.Dot('graphname', graph_type='digraph') subg = pydot.Subgraph('', rank='same') subg.add_node(pydot.Node('a')) graph.add_subgraph(subg) subg.add_node(pydot.Node('b')) subg.add_node(pydot.Node('c')) Multiple main graphs in a file are now supported, will be returned as a list of graph instances Handling of shapefiles Dot().set_shape_files() Added method "add_style()" to the Node class to easily append styles to a node Attribute lists updated to reflect the available ones in graphviz 2.16 Added error reporting when rendering graphs with GraphViz executables. There was an often reported problem where the output graphs would have 0 size. In most cases this was due to Graphviz missing a library for a format that pydot assumed to be there. Now the error given by the executable will be reported instead of being silently ignored (Thanks Jarno) Improved parsing of identifiers Added non-GraphViz attributes needed by dot2tex Jose Fonseca contributed a fix dealing with quoted strings the the dot parsing module setup.py updated so that it's possible to install pydot through Setuptools' easy_install Edge()'s can be created passing two Node objects as well as, the previously supported, two strings with node names. Warning: when passing two Node instances, the attributes won't be taken into account. The edge will only read the Nodes' names to create an edge, the Nodes must be separately added to the graph so all their attributes are "remembered". Substituted all str()'s for unicode()'s It's possible now to manually specify the path to GraphViz's executables in the case they can't be found automatically. The method 'set_graphviz_executables(paths)' will take a dictionary specifying the location of the executables. Please refer to the documentation for usage detailed information. And too many bugfixes to list... Performance: The new pydot stores graphs and their objects using a hierarchy of nested dictionaries and lists. Graph, Node, Edge objects are mere proxies to the data and are created on demand. So that now it's possible to have a graph with a 1 million edges and there will not be a single Edge instance (only if requested, then they will be created on demand, mapping the data and providing with all the methods to act on the data in the global dictionary). Storing a graph with 1 million edges in pydot 1.0 has approximately the same memory requirements (~813MiB) as dealing with one with only 40.000 edges in pydot 0.9 (~851MiB), the 40.000 edges graph needs ~35MiB in pydot 1.0 . Handling graphs should be much faster, as no linear searches are performed in pydot 1.0 Related Projectsdot2tex XDot [Less]

Generate graphviz dot files of the interactions between Biztalk odx files. Specify groups of odx files and Biztalk Visualisation will generate a graph of the orchestrations, the messages sent between ... [More] them and messages sent and received via external ports including the names and schemas of the messages. Example [Less]

This is a working tool which can be used to analyze Ant scripts (yes, more than one) to show how targets, taskdefs, macrodefs, and antcalls work together within and across Ant scripts to perform your ... [More] build. The documentation for the current version and Java WebStart download are found at http://ant-script-visualizer.googlecode.com/svn/trunk/webstart/index.html ATT's GraphViz is currently needed to generate the final graph (I'm not that smart yet): http://www.graphviz.org/ One of the interesting things about this code is I'm not using the Ant libraries to do this - I get much more flexibility and power parsing the XML myself via JDOM, and it lets me do a lot more of playing around with run-time properties and such. Although this project works as-is, I've got a long list of features and improvements that need to be made (which I could use help with), and folks have asked to download the source, so open sourcing it is a good option. [Less]

Coordinated Graph Visualization

VizierFX is a Flex library for drawing network graphs. The graphs are laid out using GraphViz on the server side, then passed to VizierFX to perform the rendering. The library also provides the ... [More] ability to run ActionScript code in response to events on the graph, such as mousing over a node or clicking on it. For more details, check out the VizierFX site at http://www.markandrewgoetz.com/vizierfx/. [Less]

Main project: Mapping,discovering relations and mining conclusive data from social networks. There are various other projects meant as utilities or code that can be re-used in some projects.

DescriptionDagvis is a prototype application that allows you to open and view workflow DAGs produced by Virolab's exp2workflow project. It is developed with execution workflows in mind, although in ... [More] theory it can read and present any GraphViz file and provide some interactivity. A computer program (the one without infinite loops) is a great example of a DAG, so no matter how complex it is, the execution always follows one of the paths of flow. A concept of a visualization of this flow can be imagined, where computation intensive tasks are represented as large vertices and data flow as edges. That leads us to new ideas: monitoring bottlenecks, interactive manual scheduling, or even bringing some real-world concepts into a mathematical creature called a DAG. Like annealing, diffusion, mapping weights of edges to network connections based on bandwidth automatically with a help from router infrastructure, state management. Important udpateJGraphX - the next version (and rewrite) of JGraph library, which is used in implementation of view layer was released on 20 X 2009. If a future developer wants to use it, he/she has to reimplement pl.cyfronet.virolab.dagvis.view.Viewer interface. See DesignOverview and DesignDetails wiki pages. Related projectsVirolab exp2workflow DocumentationSee wiki section. InstallationAndUsage - Tutorial on using the application. Configuration Technologies Requirements DesignOverview DesignDetails EventAPI FutureWork ClassDiagrams SequentialDiagrams UseCase Screenshots ScreenshotsOld A screenshot [Less]