Shift overflow counter: Difference between revisions

From BusyBeaverWiki
Jump to navigation Jump to search
add common abbr
Polygon (talk | contribs)
Examples: this one also halts
 
Line 10: Line 10:
== Examples ==
== Examples ==
* Skelet holdouts: [[Skelet 34]], [[Skelet 33]], [[Skelet 35]], [[Skelet 15]], [[Skelet 26]]
* Skelet holdouts: [[Skelet 34]], [[Skelet 33]], [[Skelet 35]], [[Skelet 15]], [[Skelet 26]]
* {{TM|1RB0RF_1LC1RB_0RD0LB_---0LE_1RE0RA_1RD1RE}}


Halting shift-overflow counters:
Halting shift-overflow counters:
* {{TM|1RB0RF_1LC1RB_0RD0LB_---0LE_1RE0RA_1RD1RE|halt}}
* {{TM|1RB1LD_1RC0RB_1LA0LE_1LC0LA_1RZ1RB|halt}}
* {{TM|1RB1LD_1RC0RB_1LA0LE_1LC0LA_1RZ1RB|halt}}
* {{TM|1RB1LD_1RC0RB_1LA1LE_1LC0LA_1RZ0RD|halt}}
* {{TM|1RB1LD_1RC0RB_1LA1LE_1LC0LA_1RZ0RD|halt}}

Latest revision as of 10:53, 21 February 2026

Shift overflow counter (SOC) is an informal class of Turing machines. A typical Turing machine in this class has the following behavior:

  • It represents digits as short fixed-length blocks of symbols.
  • It spends most of its time implementing basic double counter until one of the sides overflows (expands) which leads to changing the offsets of blocks, making them non-valid representations of digits.
  • After “Counter Phase” there is a “Reset Phase” where the contents are “reparsed”, creating a new double counter configuration. The new configuration could lead to halting.

Note: some examples (like the halting shift-overflow counters below) use a counter on one side and a bouncer (sometimes called unary counter) on the other.

Examples

Halting shift-overflow counters:

Related links