Differences between revisions 3 and 4
 ⇤ ← Revision 3 as of 2007-01-16 20:10:34 → Size: 1427 Editor: anonymous Comment: ← Revision 4 as of 2007-02-16 05:15:07 → ⇥ Size: 1210 Editor: anonymous 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...). * 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. Line 13: Line 11: The ["SAGE"] 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. The graph class supports plotting via matplotlib, and soon will also support Tachyon plotting. In addition, the migration of NetworkX 0.32 -> 0.33 must be tested. Boundary nodes (soon to be implemented) will default to plot a different color, and edge labels will be supported. Pending another graphics primitive, soon graphics objects can be associated with nodes so that in 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)}}}

## 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)

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