Kinetic data structure

Short description: Data structures used to track continuously moving geometric bodies

A kinetic data structure is a data structure used to track an attribute of a geometric system that is moving continuously.[1][2][3][4] For example, a kinetic convex hull data structure maintains the convex hull of a group of n moving points. The development of kinetic data structures was motivated by computational geometry problems involving physical objects in continuous motion, such as collision or visibility detection in robotics, animation or computer graphics.

## Contents

* 1 Overview
* 2 Contrast with traditional data structures
* 3 Certificates approach
* 3.1 Types of events
* 4 Performance
* 4.1 Responsiveness
* 4.2 Locality
* 4.3 Compactness
* 4.4 Efficiency
* 5 Discrete-time operation
* 6 In practice
* 7 Open problems
* 8 Types of trajectories
* 9 Examples
* 10 References

## Overview

Kinetic data structures are used on systems where there is a set of values that are changing as a function of time, in a known fashion. So the system has some values, and for each value v, it is known that v=f(t). Kinetic data structures allow queries on a system at the current virtual time t, and two additional operations:

* advance(t): Advances the system to time t.
* change(v,f(t)): Alters the trajectory of value v to f(t), as of the current time.

Additional operations may be supported. For example, kinetic data structures are often used with a set of points. In this case, the structure typically allows points to be inserted and deleted.

## Contrast with traditional data structures

A kinetic data structure allows the values stored in it to change continuously with time. In principle, this can be approximated by sampling the position of the points at fixed intervals of time, and deleting and re-inserting each point into a "static" (traditional) data structure. However, such an approach is vulnerable to oversampling or undersampling, depending on what interval of time is used, and can also be wasteful of computational resources.

## Certificates approach

The following general approach can be used to construct kinetic data structures:[5]

1. Store a data structure on the system at the current time t. This data structure allows queries on the system at the current virtual time.
2. Augment the data structure with certificates. Certificates are conditions under which the data structure is accurate. The certificates are all true now, and the data structure will only cease to be accurate when one of the certificates is no longer true.
3. Compute the failure time of each certificate, the time when it will cease to be true.
4. Store the certificates in a priority queue, keyed by their failure times
5. To advance to time t, look at the certificate with the lowest failure time from the priority queue. If the certificate fails before time t, pop it from the queue and fix the data structure so it is accurate at the time of failure, and update the certificates. Repeat this until the certificate with the lowest failure time in the priority queue fails after time t. If the certificate with the lowest failure time in the priority queue fails after time t, then all certificates are true at time t so the data structure can correctly answer queries at time t.

The approach can be summarized in pseudocode as follows. The data structure `D` is valid at the current time `now` and is augmented with a priority queue `Q` of certificates keyed by failure time:

function advance(t):
while Q is not empty and minFailureTime(Q) ≤ t:
c := extractMin(Q)              (the failing certificate)
now := failureTime(c)
repair D so it is accurate at time now
remove invalidated certificates from Q
compute failure times of the new certificates
insert the new certificates into Q
now := t                            (all certificates now hold at t)

function change(v, f):            (trajectory change, as of time now)
for each certificate c in Q involving v:
recompute failureTime(c) and update its key in Q

The number of certificates involving any one value, which bounds the work performed by `change`, is the locality of the structure.

### Types of events

Certificate failures are referred to as "events". An event is considered internal if the property maintained by the kinetic data structure does not change when the event occurs. An event is considered external if the property maintained by the data structure changes when the event occurs.

## Performance

When using the certificates approach, there are four measures of performance. We say a quantity is small if it is a polylogarithmic function of n, or is O(nϵ) for arbitrarily small ϵ, where n is the number of objects:

### Responsiveness

Responsiveness is the worst case amount of time required to fix the data structure and augmenting certificates when a certificate fails. A kinetic data structure is responsive if the worst case amount of time required for an update is small.

### Locality

The maximum number of certificates any one value is involved in. For structures involving moving points, this is that maximum number of certificates any one point is involved in. A kinetic data structure is local if the maximum number of certificates any one value is involved with is small.

### Compactness

The maximum number of certificates used to augment the data structure at any time. A kinetic data structure is compact if the number of certificates it uses is O(npolylog⁡n) or O(n1+ϵ) for arbitrarily small ϵ. (a small factor more than linear space)

### Efficiency

The ratio of the worst case number of events that can occur when the structure is advanced to t=∞ to the worst case number of "necessary changes" to the data structure. The definition of "necessary changes" is problem dependent. For example, in the case of a kinetic data structure maintaining the kinetic hull of a set of moving points, the number of necessary changes would be the number of times the kinetic hull changes as time is advanced to t=∞. A kinetic data structure is said to be efficient if this ratio is small.

## Discrete-time operation

The certificates approach assumes events are processed one at a time, in order, at their exact real-valued failure times. Many systems that track moving objects, such as physical simulations and game servers, instead observe the world at fixed time steps. Between observations, several certificates may fail, so the data structure must repair a batch of failures at each step rather than a single failure at an exact time. Guibas identifies recovery after multiple certificate failures as a structural open problem for the framework.[2]

A related subtlety is that a certificate set can constitute a historical proof: it certifies the attribute only in combination with the fact that no certificate failed earlier in the motion. If the system can change between observations, an absolute proof, a certificate set that validates the attribute in any state of the world, may be required instead.[2]

When trajectories are known and failure times are quantized to integer time steps, the priority queue of certificates can be replaced by a bucket queue indexed by step number, reducing event scheduling and extraction to constant time per operation.[6]

## In practice

Implementations of kinetic data structures must compute certificate failure times by finding roots of polynomials, which raises numerical robustness issues absent from the theoretical model, where exact constant-time root finding is assumed. Russel studied exact and filtered approaches to event scheduling and the practical costs of maintaining the event queue in implementations of kinetic Delaunay triangulations and related structures.[7]

Kinetic approaches to collision detection can bound the number of events by the relative separation of the objects rather than by a fixed sampling rate, avoiding both oversampling and undersampling.[8] In interactive applications such as games and physics engines, the widely used sweep and prune broad-phase algorithm maintains sorted orders of bounding-box extrema and repairs them incrementally as objects move, and can be viewed as a kinetic data structure whose certificates are the adjacencies in the sorted orders.[9]

A practical obstacle to wider adoption is the cost of trajectory changes: every certificate involving an object must be re-evaluated when that object's motion changes, which the locality measure is designed to bound.[2] Hierarchical motion descriptions, in which nearby objects share motion components, have been proposed to reduce this cost.[2]

## Open problems

Guibas's survey lists several problems that remain open, including finding an efficient, responsive, local, and compact kinetic data structure for the convex hull of points moving in dimension three or higher; tightening the gap between the quadratic lower bound and near-cubic upper bound on the number of kinetic Voronoi diagram events; maintaining a kinetic Euclidean minimum spanning tree with a subquadratic number of events; and developing motion-sensitive analyses whose costs are parameterized by the coherence of the motion rather than by the worst case.[2] Structural questions include recovery after multiple certificate failures and the analysis of non-canonical, history-dependent structures, for which mathematical techniques are lacking.[2]

Rahmati improved the event bound for the kinetic Euclidean minimum spanning tree in the plane from O(n4) to roughly O(n3log⁡n) up to Davenport–Schinzel factors, and posed successor problems including a kinetic Euclidean minimum spanning tree with a sub-cubic number of events and worst-case rather than amortized responsiveness for kinetic nearest-neighbor structures.[4]

## Types of trajectories

The performance of a certain kinetic data structure may be analyzed for certain types of trajectories. Typically, the following types of trajectories are considered:

* Affine:(Linear functions) f(t)=at+b
* Bounded-degree algebraic:(Polynomial functions of bounded degree) f(t)=∑i=0naiti for some fixed n.
* Pseudo-algebraic: Trajectories such that any certificate of interest flips between true and false O(1) times.

## Examples

* Kinetic tournament
* Kinetic sorted list
* Kinetic heap
* Kinetic convex hull
* Kinetic closest pair
* Kinetic minimum spanning tree
* Kinetic Euclidean minimum spanning tree
* Kinetic Yao graph[4]
* Kinetic Semi-Yao graph (a variant of the theta graph)[4]
* Kinetic all nearest neighbors[4]
* Kinetic all k-nearest neighbors[4]

## References

1. ↑ Basch, Julien (1999). Kinetic Data Structures (Thesis). Stanford University.
2. ↑ 2.0 2.1 2.2 2.3 2.4 2.5 2.6 Guibas, Leonidas J. (2001), "Kinetic Data Structures", in Mehta, Dinesh P.; Sahni, Sartaj, Handbook of Data Structures and Applications, Chapman and Hall/CRC, pp. 23-1–23-18, ISBN 978-1-58488-435-4, http://graphics.stanford.edu/projects/lgl/papers/g-KDS_DS-Handbook-04/g-KDS_DS-Handbook-04.pdf
3. ↑ Abam, Mohammad Ali (2007). New Data Structures and Algorithms for Mobile Data (Thesis). Eindhoven University of Technology. Archived from the original on 2020-06-08. Retrieved 2015-05-14.
4. ↑ 4.0 4.1 4.2 4.3 4.4 4.5 Rahmati, Zahed (2014). Simple, Faster Kinetic Data Structures (Thesis). University of Victoria. hdl:1828/5627.
5. ↑ Guibas, Leonidas J. (1998), "Kinetic Data Structures: A State of the Art Report", in Agarwal, Pankaj K.; Kavraki, Lydia E.; Mason, Matthew T., Robotics: The Algorithmic Perspective (Proceedings of the 3rd Workshop on the Algorithmic Foundations of Robotics), A K Peters/CRC Press, pp. 191–209, ISBN 978-1-56881-081-2, http://graphics.stanford.edu/courses/cs428-03-spring/Papers/readings/CollaborativeProcessing/g-kds.pdf
6. ↑ Brown, Randy (1988), "Calendar queues: a fast O(1) priority queue implementation for the simulation event set problem", Communications of the ACM 31 (10): 1220–1227, doi:10.1145/63039.63045
7. ↑ Russel, Daniel (2007). Kinetic Data Structures in Practice (Thesis). Stanford University.
8. ↑ Erickson, Jeff; Guibas, Leonidas J.; Stolfi, Jorge; Zhang, Li (1999), "Separation-sensitive collision detection for convex objects", Proceedings of the 10th ACM-SIAM Symposium on Discrete Algorithms (SODA '99), pp. 102–111
9. ↑ Cohen, Jonathan D.; Lin, Ming C.; Manocha, Dinesh; Ponamgi, Madhav (1995), "I-COLLIDE: an interactive and exact collision detection system for large-scale environments", Proceedings of the 1995 Symposium on Interactive 3D Graphics, pp. 189–196, doi:10.1145/199404.199437

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Kinetic data structure. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Kinetic_data_structure&oldid=4566277"