In computer science, a graph is an abstract data type that is meant to implement the graph and hypergraph concepts from mathematics.
A graph data structure consists of a finite (and possibly mutable) set of ordered pairs, called edges or arcs, of certain entities called nodes or vertices. As in mathematics, an edge (x,y) is said to point or go from x to y. The nodes may be part of the graph structure, or may be external entities represented by integer indices or references.
A graph data structure may also associate to each edge some edge value, such as a symbolic label or a numeric attribute (cost, capacity, length, etc.).
Contents |
Graph algorithms are a significant field of interest within computer science. Typical higher-level operations associated with graphs are: finding a path between two nodes, like depth-first search and breadth-first search and finding the shortest path from one node to another, like Dijkstra's algorithm. A solution to finding the shortest path from each node to every other node also exists in the form of the Floyd–Warshall algorithm.
A directed graph can be seen as a flow network, where each edge has a capacity and each edge receives a flow. The Ford–Fulkerson algorithm is used to find out the maximum flow from a source to a sink in a graph.
The basic operations provided by a graph data structure G usually include:
adjacent
(G, x, y): tests whether there is an edge from node x to node y.neighbors
(G, x): lists all nodes y such that there is an edge from x to y.add
(G, x, y): adds to G the edge from x to y, if it is not there.delete
(G, x, y): removes the edge from x to y, if it is there.get_node_value
(G, x): returns the value associated with the node x.set_node_value
(G, x, a): sets the value associated with the node x to a.Structures that associate values to the edges usually also provide:
get_edge_value
(G, x, y): returns the value associated to the edge (x,y).set_edge_value
(G, x, y, v): sets the value associated to the edge (x,y) to v.Different data structures for the representation of graphs are used in practice:
The following table gives the time complexity cost of performing various operations on graphs, for each of these representations. In the matrix representations, the entries encode the cost of following an edge. The cost of edges that are not present are assumed to be .
Adjacency list | Incidence list | Adjacency matrix | Incidence matrix | |
---|---|---|---|---|
Storage | ||||
Add vertex | ||||
Add edge | ||||
Remove vertex | ||||
Remove edge | ||||
Query: are vertices u, v adjacent? (Assuming that the storage positions for u, v are known) | ||||
Remarks | When removing edges or vertices, need to find all vertices or edges | Slow to add or remove vertices, because matrix must be resized/copied | Slow to add or remove vertices and edges, because matrix must be resized/copied |
Adjacency lists are generally preferred because they efficiently represent sparse graphs. An adjacency matrix is preferred if the graph is dense, that is the number of edges E is close to the number of vertices squared, V2, or if one must be able to quickly look up if there is an edge connecting two vertices.[1]
|