Distance oracle
In computing, a distance oracle is a data structure for calculating distances between vertices in a graph.
Introduction
Let G(V,E) be an undirected, weighted graph, with n=|V| nodes and m=|E| edges. We would like to answer queries of the form "what is the distance between the nodes s and t?".
One way to do this is just run the Dijkstra algorithm. This takes time , and requires no extra space (besides the graph itself).
In order to answer many queries more efficiently, we can spend some time in pre-processing the graph and creating an auxiliary data structure.
A simple data structure that achieves this goal is a matrix which specifies, for each pair of nodes, the distance between them. This structure allows us to answer queries in constant time , but requires extra space. It can be initialized in time using an all-pairs shortest paths algorithm, such as the Floyd–Warshall algorithm.
The distance oracle lies between these two extremes. It less than space in order to answer queries in less than time.
Thorup and Zwick approximate distance oracle
Thorup and Zwick presented[1] a data structure that, for every k, requires space , such that any subsequent distance query can be approximately answered in time . The approximate distance returned is of stretch at most , that is, the quotient obtained by dividing the estimated distance by the actual distance lies between 1 and . The initialization time is .
Some special cases include:
- For we get the simple distance matrix.
- For we get a structure using space which answers each query in constant time and approximation factor at most 3.
- For Failed to parse (unknown function "\floor"): {\displaystyle k=\floor \log n \rfloor} , we get a structure using space, query time , and stretch .
Higher values of k do not improve the space or preprocessing time.
References
- ^ Attention: This template ({{cite doi}}) is deprecated. To cite the publication identified by doi:10.1145/1044731.1044732, please use {{cite journal}} (if it was published in a bona fide academic journal, otherwise {{cite report}} with
|doi=10.1145/1044731.1044732
instead.