Knuth's up-arrow notation
From Wikipedia, the free encyclopedia
|
In mathematics, Knuth's up-arrow notation is a method of notation of very large integers introduced by Donald Knuth in 1976. It is closely related to the Ackermann function. The idea is based on iterated exponentiation in much the same way that exponentiation is iterated multiplication, and multiplication is iterated addition.
IntroductionMultiplication by a natural number can be defined as iterated addition:
can be defined as iterated multiplication:
According to this definition,
(just writing out this number in expanded form would require about 1.37 terabytes of storage space, i. e. Failed to parse (Missing texvc executable; please see math/README to configure.): 7,625,597,484,987 \times \frac{\log 3}{\log 2} bits)
This already leads to some fairly large numbers, but Knuth extended the notation. He went on to define a “triple arrow” operator for iterated application of the “double arrow” operator (also known as pentation):
Failed to parse (Missing texvc executable; please see math/README to configure.): 3\uparrow\uparrow\uparrow2 = 3\uparrow\uparrow3 = 3^{3^3} = 3^{27}=7,625,597,484,987
NotationIn expressions such as Failed to parse (Missing texvc executable; please see math/README to configure.): a^b , the notation for exponentiation is usually to write the exponent Failed to parse (Missing texvc executable; please see math/README to configure.): b as a superscript to the base number Failed to parse (Missing texvc executable; please see math/README to configure.): a . But many environments — such as programming languages and plain-text e-mail — do not support such two-dimensional layout. People have adopted the linear notation Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow b for such environments; the up-arrow suggests 'raising to the power of'. If the character set doesn't contain an up arrow, the caret ^ is used instead. The superscript notation Failed to parse (Missing texvc executable; please see math/README to configure.): a^b doesn't lend itself well for generalization, which explains why Knuth chose to work from the inline notation Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow b instead. In the context of the C programming language, the ^ character is the XOR operator. ** is a common alternative to Failed to parse (Missing texvc executable; please see math/README to configure.): \uparrow for discussion in this context, using the same principle of two symbols meaning repetition of that operator. It is possible that *** could be equivalent to Failed to parse (Missing texvc executable; please see math/README to configure.): \uparrow\uparrow , but this usage is uncommon. Writing out up-arrow notation in terms of powersAttempting to write Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow \uparrow b using the familiar superscript notation gives a power tower. With b too large to write b numbers a, this requires using dots and a brace with the number b next to it, indicating the height of the power tower. Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow \uparrow \uparrow b requires a row of such power towers, separated by braces: there are b power towers, including the last with height 1, hence simply the number a. If b is too large to write all these power towers, we use dots to indicate a row of them, and for the number of power towers a "cross-brace" (the number of braces is one less). Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow \uparrow \uparrow \uparrow b requires a row of such rows of power towers; there are b rows of power towers, including the last, which consists of only one "power tower" of height 1, so is simply the number a. If b is too large to write all these rows, we use a "cross-cross-brace" with this number b next to it (the number of cross-braces is one less). And so on. Since the power notation is in direction "/", the braces are too. A row of them could be written in perpendicular direction "\", and the cross-brace too. A row of cross-braces could then extend in the direction "/", with a cross-cross-brace too, etc. Example:
6 there are six power towers, including the last with height 1, hence simply the number 4; writing out the fifth power tower we have only five:
requires a "tetration tower" in the direction "\", and a brace with the number b next to it, indicating the height of the tetration tower. Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow \uparrow \uparrow \uparrow b requires a row of such tetration towers, separated by braces: there are b tetration towers, including the last with height 1, hence simply the number a. If b is too large to write all these tetration towers, we use a "cross-brace" with this number b next to it. And so on. Examples:
there are four tetration towers, including the last with height 1, hence simply the number 4; writing out the third tetration tower we have only three:
GeneralizationsSome numbers are so large that multiple arrows of Knuth's up-arrow notation become too cumbersome; then an n-arrow operator Failed to parse (Missing texvc executable; please see math/README to configure.): \uparrow^n is useful (and also for descriptions with a variable number of arrows), or equivalently, hyper operators. Some numbers are so large that even that notation is not sufficient. Graham's number is an example. The Conway chained arrow notation can then be used: a chain of three elements is equivalent with the other notations, but a chain of four or more is even more powerful.
DefinitionThe up-arrow notation is formally defined by
for all integers Failed to parse (Missing texvc executable; please see math/README to configure.): a, b, n with Failed to parse (Missing texvc executable; please see math/README to configure.): b \ge 0, n \ge 1 . All up-arrow operators (including normal exponentiation, Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow b ) are right associative, i.e. evaluation is to take place from right to left in an expression that contains two or more such operators. For example, Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow b \uparrow c = a \uparrow (b \uparrow c) , not Failed to parse (Missing texvc executable; please see math/README to configure.): (a \uparrow b) \uparrow c
is Failed to parse (Missing texvc executable; please see math/README to configure.): 3^{(3^3)}=3^{27}=7625597484987
not Failed to parse (Missing texvc executable; please see math/README to configure.): \left(3^3\right)^3=27^3=19683.
would equal Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow (a \uparrow (b - 1)) , so that Failed to parse (Missing texvc executable; please see math/README to configure.): \uparrow\uparrow would not be an essentially new operation. Right associativity is also natural because we can rewrite the iterated arrow expression Failed to parse (Missing texvc executable; please see math/README to configure.): a\uparrow^n\cdots\uparrow^na that appears in the expansion of Failed to parse (Missing texvc executable; please see math/README to configure.): a \uparrow^{n + 1}b as Failed to parse (Missing texvc executable; please see math/README to configure.): a\uparrow^n\cdots\uparrow^na\uparrow^n1 , so that all the Failed to parse (Missing texvc executable; please see math/README to configure.): a s appear as left operands of arrow operators. This is significant since the arrow operators are not commutative. Writing Failed to parse (Missing texvc executable; please see math/README to configure.): (a\uparrow ^m)^b for the bth functional power of the function Failed to parse (Missing texvc executable; please see math/README to configure.): f(n)=a\uparrow ^m n we have Failed to parse (Missing texvc executable; please see math/README to configure.): a\uparrow ^n b = (a\uparrow ^{n-1})^b 1 . The definition could be extrapolated one step, starting with Failed to parse (Missing texvc executable; please see math/README to configure.): a\uparrow^n b= ab if n = 0, because exponentiation is repeated multiplication starting with 1. Extrapolating one step more, writing multiplication as repeated addition, is not as straightforward because multiplication is repeated addition starting with 0 instead of 1. "Extrapolating" again one step more, writing addition of n as repeated addition of 1, requires starting with the number a. Compare the definition of the hyper operator, where the starting values for addition and multiplication are also separately specified. Tables of valuesComputing Failed to parse (Missing texvc executable; please see math/README to configure.): 2\uparrow^m n can be restated in terms of an infinite table. We place the numbers 2 Failed to parse (Missing texvc executable; please see math/README to configure.): n in the top row, and fill the left column with values 2. To determine a number in the table, take the number immediately to the left, then look up the required number in the previous row, at the position given by the number just taken.
Note: Failed to parse (Missing texvc executable; please see math/README to configure.): (10\uparrow)^k denotes a functional power of the function Failed to parse (Missing texvc executable; please see math/README to configure.): f(n)=10^n (the function also expressed by the suffix -plex as in googolplex). The table is the same as that of the Ackermann function, except for a shift in Failed to parse (Missing texvc executable; please see math/README to configure.): m and Failed to parse (Missing texvc executable; please see math/README to configure.): n , and an addition of 3 to all values. Computing Failed to parse (Missing texvc executable; please see math/README to configure.): 3\uparrow^m n
in the top row, and fill the left column with values 3. To determine a number in the table, take the number immediately to the left, then look up the required number in the previous row, at the position given by the number just taken.
Computing Failed to parse (Missing texvc executable; please see math/README to configure.): 10\uparrow^m n
in the top row, and fill the left column with values 10. To determine a number in the table, take the number immediately to the left, then look up the required number in the previous row, at the position given by the number just taken.
Note that for 2 ≤ n ≤ 9 the numerical order of the numbers Failed to parse (Missing texvc executable; please see math/README to configure.): 10\uparrow^m n is the lexicographical order with m as the most significant number, so for the numbers of these 8 columns the numerical order is simply line-by-line. The same applies for the numbers in the 97 columns with 3 ≤ n ≤ 99, and if we start from m = 1 even for 3 ≤ n ≤ 9,999,999,999. See alsoNotes
References
ko:크누스 윗화살표 표기법 nl:Knuths pijlomhoognotatie ja:クヌースの矢印表記 pl:Notacja strzałkowa sr:Кнутова нотација |


