Node Types

Home * Search * Node * Node Types



Node Types are classifications of nodes as expected inside a minimal alpha-beta tree, or as determined by the search. These types were first formulated by Donald Knuth and Ronald Moore when describing the alpha-beta algorithm and further analyzed by Judea Pearl. While Knuth used the terms Type 1, 2, and 3, Tony Marsland and Fred Popowich introduced the more descriptive terms PV-, Cut- and All-nodes.

Node types as established by the search are stored inside the transposition table, indicating whether the score is either exact, lower or upper bounded. Expected node types, as determined by tree topology, probing the transposition table, or comparing scores of a static evaluation considering threats, or even a reduced search or quiescence search, with the bounds, may be considered by various (parallel) search algorithms and in decisions concerning selectivity.

=PV-Nodes= PV-nodes (Knuth's Type 1) are nodes that have a score that ends up being inside the window. So if the bounds passed are [a,b], with the score returned s, abeta-alpha>1
 * All Siblings of a PV-node are expected Cut-nodes

=Cut-Nodes= Cut-nodes (Knuth's Type 2), otherwise known as fail-high nodes, are nodes in which a beta-cutoff was performed. So with bounds [a,b], s>=b. A minimum of one move at a Cut-node needs to be searched. The score returned is a lower bound (might be greater) on the exact score of the node
 * In Principal Variation Search Cut-nodes are searched with null windows
 * The child of a Cut-node is an All-node
 * The parent of a Cut-node is either a PV- or All-node
 * The ply distance of a Cut-node to its PV-ancestor is odd

=All-Nodes= All-nodes (Knuth's Type 3), otherwise known as fail-low nodes, are nodes in which no move's score exceeded alpha. With bounds [a,b], s<=a. Every move at an All-node is searched, and the score returned is an upper bound, the exact score might be less.
 * In Principal Variation Search All-nodes are searched with null windows
 * The children of an All-node are Cut-nodes
 * The parent of an All-node is a Cut-node
 * The ply distance of an All-node to its PV-ancestor is even

=Node Types in PVS=

Onno
Onno by Onno Garms determines expected node types, beside other things, to perform IID not only at PV-nodes but also at expected Cut-nodes. Onno Garms gave the following rules
 * The root node is a PV-node
 * The first child of a PV-node is a PV-node
 * The further children are searched by a scout search as CUT-nodes
 * PVS re-search is done as PV-node
 * The first node of bad pruning is a CUT-node
 * The node after a null move is a CUT-node
 * The first node of null move verification is a CUT-node
 * Internal iterative deepening does not change the node type
 * The first child of a CUT-node is an ALL-node
 * Further children of a CUT-node are CUT-nodes
 * Children of ALL-nodes are CUT-nodes

Summary
Following summary was given by Pradu Kannan similar to Onno's definition as an attempt to predict the node type before searching the node by assuming reasonably good move ordering on PV-nodes and Cut-nodes :
 * The root node is a PV-node
 * The first child of a PV-node is a PV-node
 * Children of PV-nodes that are searched with a zero-window scout search are Cut-nodes
 * Children of PV-nodes that have to be re-searched because the scout search failed high, are PV-nodes
 * The first child of a Cut-node, and other candidate cutoff moves (nullmove, killers, captures, checks, ...) is an All-node
 * A Cut-node becomes an All-node once the first and all candidate cutoff moves are searched
 * Children of All-nodes are Cut-nodes

=Number of Leaf Nodes=

Formulas
As emphasized by Daniel Shawul, the formulas for the number of leaf nodes of a certain Node type with uniform depth n and branching factor b, using floor and ceiling of n/2 (cut the ceiling, all the floor) ...

PV = 1 CUT = b^ &#8968;n/2&#8969; - 1 ALL = b^ &#8970;n/2&#8971; - 1

... are already the subexpressions ...

L = PV + CUT + ALL

... in Levin's famous formula demonstrating the odd-even effect of alpha-beta

L = b^ &#8968;n/2&#8969; + b^ &#8970;n/2&#8971; - 1

Table
Assuming a constant branching factor of 40, this results in following number of leaves:

=Quotes= Robert Hyatt on the distinction between ALL- and CUT-nodes : In CB, I used this extensively, because you never want to split at a CUT node, and want to prefer an ALL node. YBW tries to recognize an ALL node by requiring that at least one move be searched before splitting, since > 90% of CUT nodes are discovered on the first move searched. But waiting on that first move introduces some wait time, and if you knew it was an ALL node from the get-go, you could split before the first move is completed. That was the basic premise behind the iterated search and DTS algorithm in Cray Blitz ...

=See also=
 * Alpha-Beta
 * Enhanced Forward Pruning
 * Internal Iterative Deepening
 * Move Ordering
 * Odd-Even Effect
 * Principal Variation Search
 * Young Brothers Wait Concept

=Selected Publications=
 * Donald E. Knuth and Ronald W. Moore (1975). An analysis of alpha-beta pruning. Artificial Intelligence, 6:293–326, 1975. Reprinted in Selected Papers on Analysis of Algorithms by Donald E. Knuth, Published 2000, by Addison-Wesley ISBN: 1-57585-211-5
 * Igor Roizen (1981). On the Average Number of Terminal Nodes examined by Alpha-Beta. Technical Report UCLA-ENG-CSL-8108, University of California at Los Angeles, Cognitive Systems Laboratory
 * Judea Pearl (1982). The Solution for the Branching Factor of the Alpha-Beta Pruning Algorithm and its Optimality. Communications of the ACM, Vol. 25, No. 8, pp. 559-564
 * Tony Marsland, Fred Popowich (1985). Parallel Game-Tree Search. IEEE Transactions on Pattern Analysis and Machine Intelligence, Vol. 7, No. 4, pp. 442-452. 1984 pdf (Draft)
 * Mark Winands, Jaap van den Herik, Jos Uiterwijk, Erik van der Werf (2003). Enhanced forward pruning. pdf » Enhanced Forward Pruning

=Forum Posts=

2000 ...

 * ALL node definition by Alvaro Cardoso, CCC, February 21, 2003
 * Fruit - Question for Fabien by Dan Honeycutt, CCC, March 11, 2004 » Fruit, Transposition Table, Principal variation, Principal Variation Search
 * Re: Fruit - Question for Fabien by Fabien Letouzey, CCC, March 11, 2004


 * Re: Attack table by Zach Wegner, Winboard Forum, October 22, 2004 » Attack and Defend Maps

2005 ...

 * Move ordering at different (Knuth) node types by Tom Likens, Winboard Forum, February 21, 2006 » Move Ordering
 * PV based decisions by Mark Lefler, Winboard Forum, April 27, 2006
 * NMP on ALL nodes by Onno Garms, Winboard Forum, April 15, 2007 » Null Move Pruning
 * Slight enhancement to PVS by Pradu Kannan, Winboard Forum, June 10, 2007
 * Nodes type clarification by Mathieu Pagé, CCC, October 05, 2008
 * Different handling of ALL / CUT nodes by Gregory Strong, CCC, March 22, 2009

2010 ...

 * CUT" vs "ALL" nodes by Larry Kaufman, CCC, March 7, 2011
 * On internal iterative deepening by Onno Garms, CCC, March 13, 2011 » Internal Iterative Deepening, Onno
 * When does a cut-node became an all-node? by Alcides Schulz, CCC, March 27, 2012
 * CUT/ALL nodes ratio by Daniel Shawul, CCC, June 06, 2013
 * LMR at CUT nodes can be arbitrarily bad! by Michel Van den Bergh, CCC, June 20, 2013 » Late Move Reductions, Python
 * Pruning in PV nodes by Sergei S. Markoff, CCC, January 14, 2014 » Reductions, Root
 * Node Types and Thoughts On Their Application by Cheney Nattress, CCC, February 26, 2014
 * Null move pruning on PV nodes by Eric Oldre, CCC, July 22, 2014 » Null Move Pruning
 * LMP in PV nodes by Peter Österlund, CCC, December 27, 2014 » Move Count Based Pruning, Texel

2015 ...

 * Recognizing PV nodes by Martin Fierz, CCC, March 29, 2016
 * What is wrong with doing Nulls & ttcuts in a pv node ? by Mahmoud Uthman, CCC, January 21, 2017 » Null Move Pruning, PV-Nodes, Transposition Table
 * cut nodes by Folkert van Heusden, CCC, October 18, 2017 » Cut-Nodes

=External Links=
 * Analysis of Alpha-Beta Pruning from the Parallel Computing Works ebook

=References=

Up one Level