m-tree
{{Short description|Tree data structure}}
{{Technical|date=October 2021}}
In computer science, M-trees are tree data structures that are similar to R-trees and B-trees. It is constructed using a metric and relies on the triangle inequality for efficient range and k-nearest neighbor (k-NN) queries.
While M-trees can perform well in many conditions, the tree can also have large overlap and there is no clear strategy on how to best avoid overlap. In addition, it can only be used for distance functions that satisfy the triangle inequality, while many advanced dissimilarity functions used in information retrieval do not satisfy this.{{cite conference
| first = Paolo
| last = Ciaccia
|author2=Patella, Marco |author3=Zezula, Pavel
| title = M-tree An Efficient Access Method for Similarity Search in Metric Spaces
| book-title = Proceedings of the 23rd VLDB Conference Athens, Greece, 1997
| pages = 426–435
| publisher = Very Large Databases Endowment Inc.
| year = 1997
| location = IBM Almaden Research Center
| url = https://www.vldb.org/conf/1997/P426.PDF
| access-date = 2010-09-07
| id = p426
}}
Overview
File:M-tree_built_with_MMRad_split.png. Every blue sphere (leaf) is contained in a red sphere (directory nodes). Leaves overlap, but not too much; directory nodes overlap much more here.]]
As in any tree-based data structure, the M-tree is composed of nodes and leaves. In each node there is a data object that identifies it uniquely and a pointer to a sub-tree where its children reside. Every leaf has several data objects. For each node there is a radius that defines a Ball in the desired metric space. Thus, every node and leaf residing in a particular node is at most distance from , and every node and leaf with node parent keep the distance from it.
M-tree construction
= Components =
An M-tree has these components and sub-components:
- Non-leaf nodes
- A set of routing objects NRO.
- Pointer to Node's parent object Op.
- Leaf nodes
- A set of objects NO.
- Pointer to Node's parent object Op.
- Routing Object
- (Feature value of) routing object Or.
- Covering radius r(Or).
- Pointer to covering tree T(Or).
- Distance of Or from its parent object d(Or,P(Or))
- Object
- (Feature value of the) object Oj.
- Object identifier oid(Oj).
- Distance of Oj from its parent object d(Oj,P(Oj))
= Insert =
The main idea is first to find a leaf node {{mvar|N}} where the new object {{mvar|O}} belongs. If {{mvar|N}} is not full then just attach it to {{mvar|N}}. If {{mvar|N}} is full then invoke a method to split {{mvar|N}}. The algorithm is as follows:
{{algorithm-begin|name=Insert}}
Input: Node {{mvar|N}} of M-Tree {{mvar|MT}}, {{nowrap|Entry }}
Output: A new instance of {{mvar|MT}} containing all entries in original {{nowrap|{{mvar|MT}} plus }}
{{nowrap|}}'s routing objects or objects
if {{mvar|N}} is not a leaf then
{
/* Look for entries that the new object fits into */
{{nowrap|let be routing objects from 's set of routing objects }} {{nowrap|such that }}
{{nowrap|if is not empty then}}
{
/* If there are one or more entry, then look for an entry such that is closer to the new object */
{{nowrap|}}
}
else
{
/* If there are no such entry, then look for an object with minimal distance from */
/* its covering radius's edge to the new object */
{{nowrap|}}
/* Upgrade the new radii of the entry */
{{nowrap|}}
}
/* Continue inserting in the next level */
{{nowrap|return insert();}}
else
{
/* If the node has capacity then just insert the new object */
if {{mvar|N}} is not full then
{ {{nowrap|store()}} }
/* The node is at full capacity, then it is needed to do a new split in this level */
else
{ {{nowrap|split()}} }
}
{{algorithm-end}}
= Split =
If the split method arrives to the root of the tree, then it choose two routing objects from {{mvar|N}}, and creates two new nodes containing all the objects in original {{mvar|N}}, and store them into the new root. If split methods arrives to a node {{mvar|N}} that is not the root of the tree, the method choose two new routing objects from {{mvar|N}}, re-arrange every routing object in {{mvar|N}} in two new nodes and , and store these new nodes in the parent node of original {{mvar|N}}. The split must be repeated if has not enough capacity to store . The algorithm is as follow:
{{algorithm-begin|name=Split}}
Input: Node {{mvar|N}} of M-Tree {{mvar|MT}}, {{nowrap|Entry }}
Output: A new instance of {{mvar|MT}} containing a new partition.
/* The new routing objects are now all those in the node plus the new routing object */
let be {{mvar|NN}} entries of {{nowrap|}}
if {{mvar|N}} is not the root then
{
/*Get the parent node and the parent routing object*/
{{nowrap|let be the parent routing object of {{mvar|N}}}}
{{nowrap|let be the parent node of {{mvar|N}}}}
}
/* This node will contain part of the objects of the node to be split */
Create a new node {{mvar|N'}}
/* Promote two routing objects from the node to be split, to be new routing objects */
Create new objects {{nowrap| and .}}
Promote({{nowrap|}})
/* Choose which objects from the node being split will act as new routing objects */
Partition({{nowrap|}})
/* Store entries in each new routing object */
{{nowrap|Store 's entries in {{mvar|N}} and 's entries in {{mvar|N'}}}}
if {{mvar|N}} is the current root then
{
/* Create a new node and set it as new root and store the new routing objects */
{{nowrap|Create a new root node }}
{{nowrap|Store and in }}
}
else
{
/* Now use the parent routing object to store one of the new objects */
{{nowrap|Replace entry with entry in }}
{{nowrap|if is no full then}}
{
/* The second routing object is stored in the parent only if it has free capacity */
{{nowrap|Store in }}
}
else
{
/*If there is no free capacity then split the level up*/
{{nowrap|split()}}
}
}
{{algorithm-end}}
M-tree queries
= Range query =
A range query is where a minimum similarity/maximum distance value is specified.
For a given query object {{tmath|Q \in D}} and a maximum search distance
{{tmath|r(Q)}}, the range query range(Q, r(Q)) selects all the indexed objects {{tmath|O_j}} such that {{tmath|d(O_j, Q) \le r(Q)}}.{{cite web|title=Indexing Metric Spaces with M-tree|url=http://www-db.deis.unibo.it/research/papers/SEBD97.pdf|work=Department of Computer Science and Engineering|publisher=University of Bologna|access-date=19 November 2013|author1=P. Ciaccia |author2=M. Patella |author3=F. Rabitti |author4=P. Zezula |page=3}}
Algorithm RangeSearch starts from the root node and recursively traverses all the paths which cannot be excluded from leading to qualifying objects.
{{algorithm-begin|name=RangeSearch}}
Input: Node {{mvar|N}} of M-Tree MT, {{mvar|Q}}: query object, {{nowrap|}}: search radius
Output: all the DB objects {{nowrap|such that }}
{
{{nowrap|let be the parent object of node {{mvar|N}};}}
if {{mvar|N}} is not a leaf then {
{{nowrap|for each entry() in {{mvar|N}}}} do {
{{nowrap|if }} then {
{{nowrap|Compute ;}}
{{nowrap|if }} then
{{nowrap|RangeSearch(*ptr()),{{mvar|Q}},);}}
}
}
}
else {
{{nowrap|for each entry() in {{mvar|N}}}} do {
{{nowrap|if }} then {
{{nowrap|Compute ;}}
{{nowrap|if ≤ }} then
{{nowrap|add to the result;}}
}
}
}
}
{{algorithm-end}}
- is the identifier of the object which resides on a separate data file.
- is a sub-tree – the covering tree of
= ''k''-NN queries =
See also
- Segment tree
- Interval tree - A degenerate R-tree for one dimension (usually time)
- Bounding volume hierarchy
- Spatial index
- GiST
- Cover tree
References
{{reflist}}
{{CS-Trees}}
{{Portal bar|Technology|Mathematics|Internet|Science}}
{{DEFAULTSORT:M-Tree}}
Category:Trees (data structures)