From: Thomas Walker Lynch Date: Thu, 16 Jul 2026 08:24:07 +0000 (+0000) Subject: computational Turing Machine section coming along X-Git-Url: https://git.reasoningtechnology.com/%5B%5E?a=commitdiff_plain;h=2d27e78c1c1c37ff74b94cbbd39a7c8e73447399;p=TM-2026 computational Turing Machine section coming along --- diff --git a/document/book/TM-2026.html b/document/book/TM-2026.html index 6d14c18..89fd214 100644 --- a/document/book/TM-2026.html +++ b/document/book/TM-2026.html @@ -487,11 +487,11 @@

A goal of the computation theorist in defining a Turing Machine is to make the math concise and elegant as they can make it. This notation qualifies. However, the goal of the computer architect is to make an intuitive to design and test machine that performs well. Perhaps if a computer architect were to define the computational Turing Machine, this change in emphasis would favor a different definition.

-

The following modifications will be made to the computation theoretic Turing Machine definition so as to support the uspecified symbol.

+

The following modifications will be made to the computation theoretic Turing Machine definition so as to support the unspecified symbol.

  1. Move to a Moore style programmed state controller, so that actions can be managed separately from state transitions.
  2. -
  3. Among the new explicit actions, to have two read instructions, one the control read that reads a value that is used by the next state function, and the data reads, which stores a value for later use.
  4. -
  5. To match the two read functions, the right function can specify either the control read symbol buffer, or the data read symbol buffer.
  6. +
  7. Among the new explicit actions, to have two read instructions, a state transition gating symbol read, and data symbol read, along with two variables to hold the read results.
  8. +
  9. To match the two read functions, the write function can specify which of the read buffer contents to put on the tape.
  10. If uspecified
@@ -502,40 +502,55 @@

There is a mechanical procedure for converting a Moore Machine into a Mealy Machine, and the reverse. Two such converted machines are equally expressive. Making read an explicit action, instead of having it implied by a state transition, increases the number of states in a controller, and consequently the numbers of steps that must be taken. However, the new machine can do in two steps, anything the former machine could do in one, consequently this change affects the multiplier constant on the linear term of the step count formula, but does not change the computation complexity class determined from such a step count. The three layers of next state functions are equivalent to one layer, where the missing arguments are filled in with all possible values. This potentially increases the number of state transition arcs that must be specified, but the state transition logic and the number of states remain unchanged. Giving the specification in two parts does not change the total specification. Hence, these modifications are computationally inconsequential.

-

Turing Machine Definition, the programmable part

+

The TTCA Turing Machine fixed part

+ +

+ MF = (QF, ΣF, AF, λF) +

+ +

QF: The set of predefined states, including QF.\mathtt{initial} and QF.\mathtt{unspecified\_decision}.

+ +

ΣF: The set of predefined symbols, including ΣF.\mathtt{unspecified} and ΣF.\mathtt{left\_of\_leftmost}.

+ +

AF: The set of available actions {\mathtt{no\_op}, \mathtt{left}, \mathtt{right}, \mathtt{write\_\sigma}(\sigma), \mathtt{write\_d}, \mathtt{write\_g}}, where \mathit{symbol} must be in Σ.

+ +

λF: The predefined action table. A set of pairs of the form \langle q_0, a \rangle, where q_0 is the current state, and a is a member of AF.

+ + +

The TTCA Turing Machine variables

- M = (Q, \Sigma, κ, A, \lambda, \delta, q_0, q_h, q_e) + MV = (q, d, g) -

Where the components are redefined to strictly model a Moore machine organization:

+

q: is the current state of the machine. +

d: is the data register. +

g: is the gate register. -

+

The TTCA Turing Machine in total

-

- By separating the operational action \lambda from the transition evaluation \delta, the tuple accurately reflects a Moore machine organization. The action is securely bound to the state itself, exactly matching an architecture where each entry in the state dictionary executes one machine action before resolving the next state list. -

+

+ M = (Q, Σ, A, λ, δ, δ_0, δ_00) +

The Turing Machine architecture/organization