The busy beaver game asks, for a Turing machine limited to a fixed number of internal states, how many steps it can run before halting, or how many symbols it can write, given that it is required to eventually stop rather than loop forever. The mathematician Tibor Rado introduced the problem in his 1962 paper On Non-Computable Functions, defining two functions, one for the maximum output and one for the maximum running time, both measured across every possible halting machine of a given size. Both functions grow faster than any function that can itself be computed by an algorithm, which makes them impossible to compute in general, and this connects the busy beaver problem directly to the halting problem at the foundation of computability theory. Because the functions grow so explosively, finding the exact value for even a modestly sized busy beaver machine can, in principle, require settling open mathematical questions such as Goldbach's conjecture or the Riemann hypothesis.
Facts
Connections
Associated With
Source Wikipedia: Busy beaver
Attributed To
Source Wikipedia: Busy beaver
In Branch
Source Wikipedia: Busy beaver
Is Kind Of Object
Sources
1. Wikipedia: Busy beaver
Lead section
The concept of a busy beaver was first introduced by Tibor Radó in his 1962 paper, "On Non-Computable Functions".
Functions
In his original 1962 paper, Radó defined two functions related to the busy beaver game: the score function Σ(n) and the shifts function S(n).
Associated With: Turing Machine, Technical definition
The n-state busy beaver game (or BB-n game), introduced in Tibor Radó's 1962 paper, involves a class of Turing machines, each member of which is required to meet the following design specifications: "Running" the machine consists of starting in the starting state, with the current tape cell being any cell of a blank (all-0) tape, and then iterating the transition function until the Halt state is entered (if ever).
Attributed To: Tibor Radó, Lead sentence, attribution
first introduced by Tibor Radó in his 1962 paper
View the SourceReader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.