User:Chsam27/vp tree edit
 | This is not a Wikipedia article: It is an individual user's work-in-progress page, and may be incomplete and/or unreliable. For guidance on developing this draft, see Wikipedia:So you made a userspace draft. Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
New article name goes here new article content ...
Understanding a Vp-Tree
[edit]The way a VP-tree stores data can be represented by a circle.[1] First, understand that each node of this tree contains an input point and a radius. All the left children of a given node are the points inside the circle and all the right children of a given node are outside of the circle. The tree itself does not need to know any other information about what is being stored. All it needs is the distance function that satisfies the properties of the metric space.[1] Just imagine a circle with a radius. The left children are all located inside the circle and the right children are located outside the circle.
Searching through a VP-tree
[edit]Suppose there is a need to find the two nearest targets from a given point (The point will be placed relatively close to distance). Since there are no points yet, it is assumed that the middle point (center) is the closest target. Now a variable is needed to keep track of the distance X (This will change if another distance is greater). To determine whether we go to left or right child will depend on the given point. [1]Since the point is closer to the radius than the outer shell, search the left child. Otherwise, search the right child. Once the point (the neighbor) is found, the variable will be updated because the distance has increased.
From here, all the points within the radius have been considered. To complete the search, we will now find the closest point outside the radius (right child) and determine the second neighbor. The search method will be the same, but it will be for the right child.[1]
Advantages of a VP-Tree
[edit]- Instead of inferring multidimensional points for domain before the index being built, we build the index directly based on the distance.[1] Doing this, avoids pre-processing steps.
- Updating a VP-tree is relatively easy compared to the fast-map approach. For fast maps, after inserting or deleting data, there will come a time when fast-map will have to rescan itself. That takes up too much time and it is unclear to know when the rescanning will start.
- Distance based methods are flexible. It is “able to index objects that are represented as feature vectors of a fixed number of dimensions."[1]
References
[edit]- ^ a b c d e f Fu, Ada Wai-chee (2000). "Dynamic vp-tree indexing for n-nearest neighbor search given pair-wise distances". The VLDB Journal — The International Journal on Very Large Data Bases. Springer-Verlag New York, Inc. Secaucus, NJ, USA. pp. 154–173. vp. Retrieved 2012-10-02.
{{cite conference}}: Unknown parameter|coauthors=ignored (|author=suggested) (help)