BB(6): Difference between revisions

From BusyBeaverWiki
Jump to navigation Jump to search
m (return key not playing nicely with inline code block)
(→‎Top Halters: Added "halt" to bbch-links of top halters)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
The 6-state, 2-symbol Busy Beaver problem, '''BB(6)''', refers to the unsolved 6<sup>th</sup> value of the [[Busy Beaver function]]. With the discovery of the [[Cryptid]] machine [[Antihydra]] in June 2024, we now know that we must solve a [[Collatz-like]] problem in order to solve BB(6) and thus [https://www.sligocki.com/2024/07/06/bb-6-2-is-hard.html BB(6) is Hard].
The 6-state, 2-symbol Busy Beaver problem, '''BB(6)''', refers to the unsolved 6<sup>th</sup> value of the [[Busy Beaver function]]. With the discovery of the [[Cryptid]] machine [[Antihydra]] in June 2024, we now know that we must solve a [[Collatz-like]] problem in order to solve BB(6) and thus [https://www.sligocki.com/2024/07/06/bb-6-2-is-hard.html BB(6) is Hard].


The current BB(6) champion {{TM|1RB1RA_1RC1RZ_1LD0RF_1RA0LE_0LD1RC_1RA0RE|halt}} was discovered by mxdys in June 2025, proving the lower bound:
The current BB(6) [[champion]] {{TM|1RB1RA_1RC1RZ_1LD0RF_1RA0LE_0LD1RC_1RA0RE|halt}} was discovered by mxdys in June 2025, proving the lower bound:


<math display="block">S(6) > \Sigma(6) > 2 \uparrow\uparrow\uparrow 5</math>
<math display="block">S(6) > \Sigma(6) > 2 \uparrow\uparrow\uparrow 5</math>
Line 17: Line 17:
and also compute the remainder mod 3 of numbers produced by applying these rules 15 times (which requires some fancy math related to [[wikipedia:Euler's_totient_function|Euler's totient function]]).  
and also compute the remainder mod 3 of numbers produced by applying these rules 15 times (which requires some fancy math related to [[wikipedia:Euler's_totient_function|Euler's totient function]]).  


We are also applying existing automatic deciders, such as the Ligockis' Enumerate.py and @Iijil's MITMWFAR, on current holdout lists with more extreme choices of parameters (more computational resources). @XnoobSpeakable was able to solve 12 of the final 2728 holdouts using higher order parameters with Enumerate.py. An example command line entry is:<syntaxhighlight>
We are also applying existing automatic deciders on current holdout lists with more extreme choices of parameters (more computational resources). @XnoobSpeakable was able to solve 11 of the final 2728 holdouts using higher order parameters with the Ligockis' Enumerate.py. An example command line entry is:<syntaxhighlight>
python3 Code/Enumerate.py --infile "bb6in/bb6tm{i}.txt" --outfile "bb6out/t{i}.pb" -r --no-steps --exp-linear-rules --max-loops=50_000_000 --block-mult=3 --max-block-size=100 --time=500 --force --save-freq=1
python3 Code/Enumerate.py --infile "bb6in/bb6tm{i}.txt" --outfile "bb6out/t{i}.pb" -r --no-steps --exp-linear-rules --max-loops=50_000_000 --block-mult=3 --max-block-size=100 --time=500 --force --save-freq=1
</syntaxhighlight>For context, during the Stage 2 BB(7) enumeration, where speed was more important due to the tens of millions of known holdouts, parameters of <code>--max-loops=100_000 --block-mult=2 --time=30 --save-freq=100</code> were used. @Xnoob ran Enumerate.py on all TMs in the 2728 holdout list with the above max-loops and max-block-size parameters using <code>--block-mult=1</code> ,<code>--block-mult=2</code> , and <code>--block-mult=3</code>. Andrew Ducharme started running MITMWFAR code on the 2728 holdout list with the command line entry<syntaxhighlight>
</syntaxhighlight>@XnoobSpeakable ran Enumerate.py on all TMs in the 2728 holdout list with the above max-loops and max-block-size parameters using <code>--block-mult=1</code> ,<code>--block-mult=2</code> , and <code>--block-mult=3</code>. For context, during the Stage 2 BB(7) enumeration, where speed was more important due to the tens of millions of known holdouts, parameters of <code>--max-loops=100_000 --block-mult=2 --time=30 --save-freq=100</code> were used. 
./MITMWFAR -n=N -m=M -pm=1 < ./solvable_BB6_holdouts.txt > solved_nN_mM.txt
 
</syntaxhighlight>The flags <code>-n</code> and <code>-m</code> set the number of maximum non-dead transitions scanned and the size of each weighted finite automaton's memory, respectively. Increasing n increases computation time much faster than increasing m does. The following table lists the tested combinations of parameters tried already and their (so far, disappointing) results. Blank entries mean the computation has not been attempted yet.
@Iijil's MITMWFAR decider is likely too weak to be of any assistance: running the decider on 2650 BB(6) holdouts, using parameters not strong enough to solve BB(5) TMs, took prohibitively long to compute.
{| class="wikitable"
|+Large parameter MITMWFAR results
!
!n = 9
!n = 10
!n = 11
!n = 12
!n = 13
|-
|m = 1
|0
|0
|0
|0
|
|-
|m = 2
|0
|
|
|
|
|}


== Cryptids ==
== Cryptids ==
Line 92: Line 69:
|10 ↑↑ 11010000
|10 ↑↑ 11010000
|-
|-
|{{TM|1RB0LD_1RC0RF_1LC1LA_0LE1RZ_1LF0RB_0RC0RE}}
|{{TM|1RB0LD_1RC0RF_1LC1LA_0LE1RZ_1LF0RB_0RC0RE|halt}}
|10 ↑↑ 15.60465
|10 ↑↑ 15.60465
|-
|-
|{{TM|1RB0LF_1RC1RB_1LD0RA_1LB0LE_1RZ0LC_1LA1LF}}
|{{TM|1RB0LF_1RC1RB_1LD0RA_1LB0LE_1RZ0LC_1LA1LF|halt}}
|10 ↑↑ 7.52390
|10 ↑↑ 7.52390
|-
|-
|{{TM|1RB0LF_1RC1RB_1LD0RA_1RF0LE_1RZ0LC_1LA1LF}}
|{{TM|1RB0LF_1RC1RB_1LD0RA_1RF0LE_1RZ0LC_1LA1LF|halt}}
|10 ↑↑ 7.52390
|10 ↑↑ 7.52390
|-
|-
|{{TM|1RB0LF_1RC1RB_1LD0RA_1LF0LE_1RZ0LC_1LA1LF}}
|{{TM|1RB0LF_1RC1RB_1LD0RA_1LF0LE_1RZ0LC_1LA1LF|halt}}
|10 ↑↑ 7.52390
|10 ↑↑ 7.52390
|-
|-
|{{TM|1RB1RC_1LC1RE_1LD0LB_1RE1LC_1LE0RF_1RZ1RA}}
|{{TM|1RB1RC_1LC1RE_1LD0LB_1RE1LC_1LE0RF_1RZ1RA|halt}}
|10 ↑↑ 7.23619
|10 ↑↑ 7.23619
|-
|-
|{{TM|1RB1RA_1LC1LE_1RE0LD_1LC0LF_1RZ0RA_0RA0LB}}
|{{TM|1RB1RA_1LC1LE_1RE0LD_1LC0LF_1RZ0RA_0RA0LB|halt}}
|10 ↑↑ 6.96745
|10 ↑↑ 6.96745
|-
|-
|{{TM|1RB0RF_1LC0RA_1RZ0LD_1LE1LD_1RB1RC_0LD0RE}}
|{{TM|1RB0RF_1LC0RA_1RZ0LD_1LE1LD_1RB1RC_0LD0RE|halt}}
|10 ↑↑ 5.77573
|10 ↑↑ 5.77573
|-
|-
|{{TM|1RB0LA_1LC1LF_0LD0LC_0LE0LB_1RE0RA_1RZ1LD}}
|{{TM|1RB0LA_1LC1LF_0LD0LC_0LE0LB_1RE0RA_1RZ1LD|halt}}
|10 ↑↑ 5.63534
|10 ↑↑ 5.63534
|}
|}
Line 124: Line 101:
== References ==
== References ==
<references />
<references />
[[Category:BB Domain]]
[[Category:BB Domains]]

Latest revision as of 18:46, 16 August 2025

The 6-state, 2-symbol Busy Beaver problem, BB(6), refers to the unsolved 6th value of the Busy Beaver function. With the discovery of the Cryptid machine Antihydra in June 2024, we now know that we must solve a Collatz-like problem in order to solve BB(6) and thus BB(6) is Hard.

The current BB(6) champion 1RB1RA_1RC1RZ_1LD0RF_1RA0LE_0LD1RC_1RA0RE (bbch) was discovered by mxdys in June 2025, proving the lower bound:

Techniques

Simulating tetrational machines, such as the former champion 1RB0LD_1RC0RF_1LC1LA_0LE1RZ_1LF0RB_0RC0RE (bbch), requires accelerated simulation that can handle Collatz Level 2 inductive rules. In other words, it requires a simulator that can prove the rules:

and also compute the remainder mod 3 of numbers produced by applying these rules 15 times (which requires some fancy math related to Euler's totient function).

We are also applying existing automatic deciders on current holdout lists with more extreme choices of parameters (more computational resources). @XnoobSpeakable was able to solve 11 of the final 2728 holdouts using higher order parameters with the Ligockis' Enumerate.py. An example command line entry is:

python3 Code/Enumerate.py --infile "bb6in/bb6tm{i}.txt" --outfile "bb6out/t{i}.pb" -r --no-steps --exp-linear-rules --max-loops=50_000_000 --block-mult=3 --max-block-size=100 --time=500 --force --save-freq=1

@XnoobSpeakable ran Enumerate.py on all TMs in the 2728 holdout list with the above max-loops and max-block-size parameters using --block-mult=1 ,--block-mult=2 , and --block-mult=3. For context, during the Stage 2 BB(7) enumeration, where speed was more important due to the tens of millions of known holdouts, parameters of --max-loops=100_000 --block-mult=2 --time=30 --save-freq=100 were used.

@Iijil's MITMWFAR decider is likely too weak to be of any assistance: running the decider on 2650 BB(6) holdouts, using parameters not strong enough to solve BB(5) TMs, took prohibitively long to compute.

Cryptids

Several Turing machines have been found that are Cryptids, considered so because each of them have a Collatz-like halting problem, a type of problem that is generally difficult to solve. However, probabilistic arguments have allowed all but one of them to be categorized as probviously halting or probviously non-halting.

Probviously non-halting Cryptids:

Probviously halting Cryptids:

Although 1RB1LE_0LC0LB_1RD1LC_1RD1RA_1RF0LA_---1RE (bbch) behaves similarly to the probviously halting Cryptids, it is estimated to have a 3/5 chance of becoming a translated cycler and a 2/5 chance of halting.

There are a few machines considered notable for their chaotic behaviour, but which have not been classified as Cryptids due to seemingly lacking a connection to any known open mathematical problems, such as Collatz-like problems.

Potential Cryptids:

Top Halters

Below is a table of the machines with the 10 highest known runtimes.[1] Their sigma scores are expressed using an extension of Knuth's up-arrow notation.[2]

Top Known BB(6) Halters
Standard format (approximate) Σ
1RB1RA_1RC1RZ_1LD0RF_1RA0LE_0LD1RC_1RA0RE (bbch) 2 ↑↑↑ 5
1RB1LC_1LA1RE_0RD0LA_1RZ1LB_1LD0RF_0RD1RB (bbch) 10 ↑↑ 11010000
1RB0LD_1RC0RF_1LC1LA_0LE1RZ_1LF0RB_0RC0RE (bbch) 10 ↑↑ 15.60465
1RB0LF_1RC1RB_1LD0RA_1LB0LE_1RZ0LC_1LA1LF (bbch) 10 ↑↑ 7.52390
1RB0LF_1RC1RB_1LD0RA_1RF0LE_1RZ0LC_1LA1LF (bbch) 10 ↑↑ 7.52390
1RB0LF_1RC1RB_1LD0RA_1LF0LE_1RZ0LC_1LA1LF (bbch) 10 ↑↑ 7.52390
1RB1RC_1LC1RE_1LD0LB_1RE1LC_1LE0RF_1RZ1RA (bbch) 10 ↑↑ 7.23619
1RB1RA_1LC1LE_1RE0LD_1LC0LF_1RZ0RA_0RA0LB (bbch) 10 ↑↑ 6.96745
1RB0RF_1LC0RA_1RZ0LD_1LE1LD_1RB1RC_0LD0RE (bbch) 10 ↑↑ 5.77573
1RB0LA_1LC1LF_0LD0LC_0LE0LB_1RE0RA_1RZ1LD (bbch) 10 ↑↑ 5.63534

The runtimes are presumed to be about which is roughly indistinguishable in tetration notation.

Holdouts

Number of BB(6) holdouts over time

@mxdys's informal holdouts list has 2728 machines up to equivalence as of July 2025.

References

  1. Shawn Ligocki's list of 6-state, 2-symbol machines with large runtimes (Link)
  2. Shawn Ligocki. 2022. "Extending Up-arrow Notation"