Depth of noncommutative subrings

From formulasearchengine
Revision as of 15:10, 11 November 2013 by en>Jackfork (Reverted 1 edit by 2001:690:2200:c401::133 (talk) to last revision by 2001:690:2200:C401:0:0:0:133. (TW))
Jump to navigation Jump to search

My name is Jestine (34 years old) and my hobbies are Origami and Microscopy.

Here is my web site; http://Www.hostgator1centcoupon.info/ (support.file1.com)

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-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.[1]

Overview

2D M-Tree visualized using ELKI. The tree has a single level of leaf nodes. Due to a suboptimal split heuristic, there is a large overlap.

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 r that defines a Ball in the desired metric space. Thus, every node n and leaf l residing in a particular node N is at most distance r from N, and every node n and leaf l with node parent N keep the distance from it.

M-Tree construction

Components

An M-Tree has these components and sub-components:

  1. Non-leaf nodes
    1. A set of routing objects NRO.
    2. Pointer to Node's parent object Op.
  2. Leaf nodes
    1. A set of objects NO.
    2. Pointer to Node's parent object Op.
  3. Routing Object
    1. (Feature value of) routing object Or.
    2. Covering radius r(Or).
    3. Pointer to covering tree T(Or).
    4. Distance of Or from its parent object d(Or,P(Or))
  4. Object
    1. (Feature value of the) object Oj.
    2. Object identifier oid(Oj).
    3. Distance of Oj from its parent object d(Oj,P(Oj))

Insert

The main idea is first to find a leaf node N where the new object O belongs. If N is not full then just attach it to N. If N is full then invoke a method to split N. The algorithm is as follows:

Template:Algorithm-begin

  Input: Node N  of M-Tree MT, Entry On
  Output: A new instance of MT containing all entries in original MT plus On
  NeN's routing objects or objects
  if N is not a leaf then
  {
       /*Look for entries that the new object fits into*/
       let Nin be routing objects from Ne's set of routing objects NRO such that d(Or,On)<=r(Or)
       if Nin is not empty then
       {
          /*If there are one or more entry, then look for an entry such that is closer to the new object*/
          Or=minOrNind(Or,On)
       }
       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*/
          Or=minOrNind(Or,On)r(Or)
          /*Upgrade the new radii of the entry*/
          r(Or) = d(Or,On)
       }
       /*Continue inserting in the next level*/
       return insert(T(Or), On);
  else
  {
       /*If the node has capacity then just insert the new object*/
       if N is not full then
       {  store(N, On)   }
       /*The node is at full capacity, then it is needed to do a new split in this level*/
       else
       {  split(N, On) }
  }

Template:Algorithm-end

Split

If the split method arrives to the root of the tree, then it choose two routing objects from N, and creates two new nodes containing all the objects in original N, and store them into the new root. If split methods arrives to a node N that is not the root of the tree, the method choose two new routing objects from N, re-arrange every routing object in N in two new nodes N1 and N2, and store this new nodes in the parent node Np of original N. The split must be repeated if Np has not enough capacity to store N2. The algorithm is as follow:

Template:Algorithm-begin

  Input: Node N  of M-Tree MT, Entry On
  Output: A new instance of MT containing a new partition.
  /*The new routing objects are now all those in the node plus the new routing object*/
  let be NN entries of NO
  if N is not the root then
  {
     /*Get the parent node and the parent routing object*/
     let Op be the parent routing object of N
     let Np be the parent node of N
  }
  /*This node will contain part of the objects of the node to be split*/
  Create a new node N
  /*Promote two routing objects from the node to be split, to be new routing objects*/
  Create new objects Op1 and Op2.
  Promote(N, Op1, Op2)
  /*Choose which objects from the node being split will act as new routing objects*/
  Partition(N, Op1, Op2, N1, N2)
  /*Store entries in each new routing object*/
  Store N1's entries in N and N2's entries in N
  if N is the current root then
  {
      /*Create a new node and set it as new root and store the new routing objects*/
      Create a new root node Np
      Store Op1 and Op2 in Np
  }
  else
  {
      /*Now use the parent rouing object to store one of the new objects*/
      Replace entry Op with entry Op1 in Np
      if Np is no full then
      {
          /*The second routinb object is stored in the parent only if it has free capacity*/
          Store Op2 in Np
      }
      else
      {
           /*If there is no free capacity then split the level up*/
           split(Np, Op2)
      }
  }

Template: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 Q ∈ D and a maximum search distance r(Q), the range query range(Q, r(Q)) selects all the indexed objects Oj such that d(Oj, Q) ≤ r(Q).[2]

Algorithm RangeSearch starts from the root node and recursively traverses all the paths which cannot be excluded from leading to qualifying objects. Template:Algorithm-begin Input: Node N of M-Tree MT, Q: query object, r(Q): search radius

Output: all the DB objects such that d(Oj,Q)r(Q)

{ let Op be the parent object of node N;

if N is not a leaf then { for each entry(Or) in N do:

          if | d(Op,Q)d(Or,Op) | ≤ r(Q)+r(Or)
          then { Compute d(Or,Q);
                      if d(Or,Q)r(Q)+r(Or)
                      then RangeSearch(ptr(T(Or)),Q,r(Q)); }}

else { for each entry(Oj) in N do:

          if | d(Op,Q)d(Oj,Op) | ≤ r(Q)
          then { Compute d(Oj,Q);
                     if d(Oj,Q)r(Q)
                     then add oid(Oj) to the result; }}}

Template:Algorithm-end

oid(Oj) is the identifier of the object which resides on a separate data file.

T(Or) is a sub-tree – the covering tree of Or

k-NN queries

K Nearest Neighbor (k-NN) query takes the cardinality of the input set as an input perimeter. For a given query object Q ∈ D and an integer k ≥ 1, the k-NN query NN(Q, k) selects the k indexed objects which have the shortest distance from Q, according to the distance function d. [2] Template:Empty section

See also

References

43 year old Petroleum Engineer Harry from Deep River, usually spends time with hobbies and interests like renting movies, property developers in singapore new condominium and vehicle racing. Constantly enjoys going to destinations like Camino Real de Tierra Adentro.

Template:CS-Trees

  1. 55 years old Systems Administrator Antony from Clarence Creek, really loves learning, PC Software and aerobics. Likes to travel and was inspired after making a journey to Historic Ensemble of the Potala Palace.

    You can view that web-site... ccleaner free download
  2. 2.0 2.1 Template:Cite web