TYBR: 2025: Difference between revisions

From BusyBeaverWiki
Jump to navigation Jump to search
m Holdouts Reductions.: Technically, the difference between holdout sizes is not equal to number of solved machines. This is because some of this reduction was finding equivalence classes. Additionally it can happen that holdout sizes actually increase because of TNF enumeration expanding a TM after it is found to halt (although this may not have happened for BB6 last year.
Polygon (talk | contribs)
BB Adjacent: added num(5)
 
(5 intermediate revisions by 3 users not shown)
Line 7: Line 7:
== This Year in Beaver Research <small><sub>(TYBR - "Thank You Beaver Researchers!")</sub></small> ==
== This Year in Beaver Research <small><sub>(TYBR - "Thank You Beaver Researchers!")</sub></small> ==


=== Holdouts Reductions. ===
=== Holdouts Reductions ===


{| class="wikitable"
{| class="wikitable"
Line 18: Line 18:
|-
|-
|[[BB(6)]]
|[[BB(6)]]
|3571
|4319
|1326
|1326
|2245
|2993
|62.87%
|69.30%
|-
|-
|[[BB(7)]]
|[[BB(7)]]
Line 36: Line 36:
|-
|-
|[[BB(2,6)]]
|[[BB(2,6)]]
|not enumerated
|22,302,296
|870,085
|870,085
|'''-'''
|21,432,211
|'''-'''
|96.10%
|-
|-
|[[BB(3,4)]]
|[[BB(3,4)]]
Line 54: Line 54:
|}
|}


* [[BB(6)]] - Reduced from '''3571''' to '''1326''' holdouts, a '''63% reduction.'''
* [[BB(6)]] - Reduced from '''4319''' to '''1326''' [[holdouts]], a '''69.30% reduction.'''
* [[BB(2,5)]] - Reduced from '''217''' to '''75,''' a '''65.43% reduction.''' (The number of informal holdouts is '''64''').
* [[BB(2,5)]] - Reduced from '''217''' to '''75,''' a '''65.43% reduction.''' (The number of informal holdouts is '''64''').
* [[BB(7)]] - '''Enumeration was completed''', the number of holdouts was reduced from an initial 85,853,789 to '''20,387,509''' machines, a '''76.25%''' reduction.
* [[BB(7)]] - '''Enumeration was completed''', the number of holdouts was reduced from an initial 85,853,789 to '''20,387,509''' machines, a '''76.25%''' reduction.
* [[BB(4,3)]] - Reduced from 460,916,384 to 9,401,447 holdouts, a '''97.96% reduction.'''
* [[BB(4,3)]] - Reduced from 460,916,384 to 9,401,447 holdouts, a '''97.96% reduction.'''
* [[BB(3,4)]] - Reduced from 434,787,751 to 12,435,284 holdouts, a '''97.14% reduction.'''
* [[BB(3,4)]] - Reduced from 434,787,751 to 12,435,284 holdouts, a '''97.14% reduction.'''
* [[BB(2,6)]] - '''Enumeration was completed''', the number of holdouts was reduced from an inital 2,278,655,696 to '''870,085''' machines, a '''near 100%''' reduction.
* [[BB(2,6)]] - Reduced from 22,302,296 to '''870,085''' holdouts, a '''96.10%''' reduction.
* [[BB(2,7)]] - '''Enumeration started''', 100K of the 1M subtasks have been enumerated ('''10%''').
* [[BB(2,7)]] - '''Enumeration started''', 100K of the 1M subtasks have been enumerated ('''10%''').


=== Champions. ===
=== Champions ===


* [[BB(6)]] - On 16 June 2025, mxdys discovered {{TM|1RB1LC_1LA1RE_0RD0LA_1RZ1LB_1LD0RF_0RD1RB|halt}}, running for 10 ↑↑ 11010000 steps. This was surpassed on 25 June when mxdys discovered {{TM|1RB1RA_1RC1RZ_1LD0RF_1RA0LE_0LD1RC_1RA0RE|halt}}, a TM which runs for <math>10 \uparrow\uparrow 10 \uparrow\uparrow 10 \uparrow\uparrow 8.10237</math> steps.
* [[BB(6)]] - On 16 June 2025, mxdys discovered {{TM|1RB1LC_1LA1RE_0RD0LA_1RZ1LB_1LD0RF_0RD1RB|halt}}, running for 10 ↑↑ 11010000 steps. This was surpassed on 25 June when mxdys discovered {{TM|1RB1RA_1RC1RZ_1LD0RF_1RA0LE_0LD1RC_1RA0RE|halt}}, a TM which runs for <math>10 \uparrow\uparrow 10 \uparrow\uparrow 10 \uparrow\uparrow 8.10237</math> steps.
Line 74: Line 74:
* [[Non-halting Turing machine#Translated cycler period|BBP(3,3)]] - On 25 Dec 2025, [[User:Azerty|Azerty]] discovered {{TM|1RB2RC1LC_0RC0RB1LA_2LA2RC1LB}} which is a [[Translated cycler]] with a new record period length of 1195 steps.
* [[Non-halting Turing machine#Translated cycler period|BBP(3,3)]] - On 25 Dec 2025, [[User:Azerty|Azerty]] discovered {{TM|1RB2RC1LC_0RC0RB1LA_2LA2RC1LB}} which is a [[Translated cycler]] with a new record period length of 1195 steps.


=== New Methods. ===
=== New Methods ===


* New FAR using DFA generator by mxdys.<sup>[https://discord.com/channels/960643023006490684/1028746861395316776/1442964185599447152 <nowiki>[1]</nowiki>][https://discord.com/channels/960643023006490684/1239205785913790465/1443990614483013632 <nowiki>[2]</nowiki>]</sup>
* New FAR using DFA generator by mxdys.<sup>[https://discord.com/channels/960643023006490684/1028746861395316776/1442964185599447152 <nowiki>[1]</nowiki>][https://discord.com/channels/960643023006490684/1239205785913790465/1443990614483013632 <nowiki>[2]</nowiki>]</sup>
Line 81: Line 81:
TODO: Before July
TODO: Before July


=== Misc. ===
=== Misc ===


* A fast algorithm for [[Consistent Collatz]] simulation was re-discovered and popularized. Using it,
* A fast algorithm for [[Consistent Collatz]] simulation was re-discovered and popularized. Using it,
Line 100: Line 100:
TODO: Before July
TODO: Before July


=== BB Adjacent. ===
=== BB Adjacent ===


* [[Instruction-Limited Busy Beaver]] was introduced and calculated up to BBi(7).
* [[Instruction-Limited Busy Beaver]] was introduced and calculated up to BBi(7).
Line 112: Line 112:
* [[Busy Beaver for lambda calculus#De Bruijn|Busy Beaver for lambda calculus using De Bruijn indexes]] was introduced with lower bounds having been calculated up to n = 34.
* [[Busy Beaver for lambda calculus#De Bruijn|Busy Beaver for lambda calculus using De Bruijn indexes]] was introduced with lower bounds having been calculated up to n = 34.
* [[Register machine|Busy Beaver for Register machines]] (MBB(n)) was introduced and computed up to n = 5 and a lower bound for n = 6 was discovered.
* [[Register machine|Busy Beaver for Register machines]] (MBB(n)) was introduced and computed up to n = 5 and a lower bound for n = 6 was discovered.
* [[Maximum Consecutive Ones Function|num(5)]] was [https://groups.google.com/g/busy-beaver-discuss/c/pvtXPmuMsAg/m/UP0xcmwoEAAJ shown to be] 165 by Andrés Sancho.


TODO: Before July and Semi-infinite tape Busy Beaver https://discord.com/channels/960643023006490684/1450894930422530161/1450894930422530161
TODO: Before July and Semi-infinite tape Busy Beaver https://discord.com/channels/960643023006490684/1450894930422530161/1450894930422530161


=== In the News. ===
=== In the News ===


* 6 January 2025. It Boltwise. [https://www.it-boltwise.de/durchbruch-im-busy-beaver-problem-eine-neue-aera-der-mathematik.html Durchbruch im Busy Beaver Problem: Eine neue Ära der Mathematik] (German) (English: Breakthrough in the Busy Beaver problem: A new era of mathematics).
* 6 January 2025. It Boltwise. [https://www.it-boltwise.de/durchbruch-im-busy-beaver-problem-eine-neue-aera-der-mathematik.html Durchbruch im Busy Beaver Problem: Eine neue Ära der Mathematik] (German) (English: Breakthrough in the Busy Beaver problem: A new era of mathematics).
Line 147: Line 148:
* 31 Dec 2025. Nick Drozd. [https://nickdrozd.github.io/2025/12/31/goalposts.html Running out of places to move the goalposts to].
* 31 Dec 2025. Nick Drozd. [https://nickdrozd.github.io/2025/12/31/goalposts.html Running out of places to move the goalposts to].


TODO: Before July


TODO: Fix referencing throughout the article
[[Category:This Year in Beaver Research|2025]]
[[Category:This Year in Beaver Research|2025]]

Latest revision as of 15:04, 19 April 2026

This is a summary research from all of 2025 (as documented in individual This Month in Beaver Research throughout the year). 2025 was a very productive year for BBChallenge: about 60% of the next domain, BB(6), was solved. Furthermore, new champions were discovered for BB(6), BB(7) and BB(4,3). Many models of computation other than Turing Machines were also explored - most notably Fractran and Instruction-Limited Busy Beaver. Some new methods were developed, such as mxdys's new version of FAR.

This year, Themed Months were introduced - first, for BB(3,3), then for BB(2,5) - and the result is the clarification and verification of some of the results and techniques on the Discord and wiki. See TMBR: November 2025#Themed Months for more information.

An annotated spreadsheet of BB(6) holdouts was also shared by Robin Rovenszky, which includes links to Discord discussions, classification of machines and is almost always up-to-date. See Google Sheets

This Year in Beaver Research (TYBR - "Thank You Beaver Researchers!")

Holdouts Reductions

BB Holdout Reduction by Domain
Domain Previous Holdout Count New Holdout Count Holdout Reduction % Reduction
BB(6) 4319 1326 2993 69.30%
BB(7) not enumerated 20,387,509 - -
BB(2,5) 217 75 142 65.44%
BB(2,6) 22,302,296 870,085 21,432,211 96.10%
BB(3,4) 434,787,751 12,435,284 422,352,467 97.14%
BB(4,3) 460,916,384 9,401,447 451,514,937 97.96%
  • BB(6) - Reduced from 4319 to 1326 holdouts, a 69.30% reduction.
  • BB(2,5) - Reduced from 217 to 75, a 65.43% reduction. (The number of informal holdouts is 64).
  • BB(7) - Enumeration was completed, the number of holdouts was reduced from an initial 85,853,789 to 20,387,509 machines, a 76.25% reduction.
  • BB(4,3) - Reduced from 460,916,384 to 9,401,447 holdouts, a 97.96% reduction.
  • BB(3,4) - Reduced from 434,787,751 to 12,435,284 holdouts, a 97.14% reduction.
  • BB(2,6) - Reduced from 22,302,296 to 870,085 holdouts, a 96.10% reduction.
  • BB(2,7) - Enumeration started, 100K of the 1M subtasks have been enumerated (10%).

Champions

New Methods

TODO: Before July

Misc

  • A fast algorithm for Consistent Collatz simulation was re-discovered and popularized. Using it,
    • apgoucher simulated Antihydra to 238 iterations. This is actually a result from one year ago, but was rediscovered and added to the wiki. Source
    • Shawn Ligocki simulated 1RB1RA_0RC1RC_1LD0LF_0LE1LE_1RA0LB_---0LC (bbch) out to one additional Collatz reset, demonstrating that (if they halt, which they probviously should) they will have sigma scores >1010107.
    • This algorithm has near linear runtime (in the number of iterations simulated), but also linear memory growth since the parameters grow exponentially. This memory limit seems to be the main bottleneck to simulating Antihydra and other Consistent Collatz iterations further. There has been some discussion on more efficient memory usage or a distributed algorithm to support further scaling, but no results are available yet.
  • Andrew Wade claims to have proven that BB(432) is independent of ZF. Source
  • Piecewise Affine Functions (PAF) were explored as a generalization of the BMO1 rules:
    • @Bard proved that 3 dimension PAF are Turing complete.[1]
    • @star proved that 2 dimension PAF are Turing complete.[2][3]
    • Shawn Ligocki wrote up a proof sketch that 2-region PAF are Turing complete.[4]
    • It was discovered that Amir Ben-Amram had already proven both of these results in 2015 (both the 2-dim and the 2-region results).
    • BMO1 is a 2-dim, 2-region PAF so this provides some sense for the difficulty of the problem.
    • This introduces a new type of Cryptids separate from previous Collatz-like ones.
  • @coda shared a mechanical implementation of Antihydra[5] and @zts439 3d-printed a prototype.[6]
  • @vonhust created a fast TM simulator that averages 2 billion steps / s. It uses fixed-block Macro Machines with each block bit-packed into integers. It is about 10x faster than direct simulators across most TMs.[7]

TODO: Before July

BB Adjacent

TODO: Before July and Semi-infinite tape Busy Beaver https://discord.com/channels/960643023006490684/1450894930422530161/1450894930422530161

In the News


TODO: Fix referencing throughout the article