Differences between revisions 1 and 5 (spanning 4 versions)
Revision 1 as of 2006-11-02 05:49:07
Size: 1049
Editor: c-24-19-47-89
Comment:
Revision 5 as of 2007-02-16 05:15:48
Size: 1231
Editor: c-67-183-21-142
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
The SAGE [http://sage.math.washington.edu:9001/graph Graph Theory Project] aims to implement Graph objects and algorithms in ["SAGE"].
Line 9: Line 7:
I'm integrating graph plotting fucntionality in ["SAGE"] one piece at a time. == 2D Plotting ==
Line 11: Line 9:
So far, after small revisions to the graphics class, I've written a NetworkX primitive that takes a NetworkX graph on initialization, and renders that graph using NetworkX's native spring layout routine. In this routine, each edge is treated as a spring; after each node is randomly placed on the plot screen, fifty iterations allow the "springs" to align themselves in equilibrium, often revealing geometric symmetries of the graph (try plotting a Platonic solid...). This is only the beginning of a true graph plotting interface, since there must be routines and objects that will deal with a soon-coming ["SAGE"] graph class. When completed, this NetworkX primitive should take advantage of as much NetworkX functionality as possible.  * matplotlib plotting is supported (albeit awkwardly) by NetworkX. Smooth interfacing of this functionality with SAGE (especially the notebook) is almost complete. Part of this implementation was writing a NetworkX graphics primitive. In this routine, each edge is treated as a spring; after each node is randomly placed on the plot screen, fifty iterations allow the "springs" to align themselves in equilibrium, often revealing geometric symmetries of the graph (try plotting a Platonic solid...). There are also options to pre-specify vertex positions: the graph class now comes with an optional positioning variable, so that if a user likes to think of a graph in a certain visual layout, that layout can be made part of the graph information. Boundary nodes default to plot a different color, and edge labels will soon be displayed. Pending another graphics primitive, graphics objects can be associated with nodes so that the plots show up in place of the nodes when a graph is displayed.

 * Examples:

{{{
graphs.CubeGraph(5).show(vertex_labels=False, node_size=100)
}}}
attachment:5-cube.png



 

TableOfContents

Introduction

Robert Miller is working on this project.

2D Plotting

  • matplotlib plotting is supported (albeit awkwardly) by NetworkX. Smooth interfacing of this functionality with SAGE (especially the notebook) is almost complete. Part of this implementation was writing a NetworkX graphics primitive. In this routine, each edge is treated as a spring; after each node is randomly placed on the plot screen, fifty iterations allow the "springs" to align themselves in equilibrium, often revealing geometric symmetries of the graph (try plotting a Platonic solid...). There are also options to pre-specify vertex positions: the graph class now comes with an optional positioning variable, so that if a user likes to think of a graph in a certain visual layout, that layout can be made part of the graph information. Boundary nodes default to plot a different color, and edge labels will soon be displayed. Pending another graphics primitive, graphics objects can be associated with nodes so that the plots show up in place of the nodes when a graph is displayed.
  • Examples:

graphs.CubeGraph(5).show(vertex_labels=False, node_size=100)

attachment:5-cube.png

graph_plotting (last edited 2008-11-14 13:42:15 by localhost)