Turing Machine Generator:

Tip

If you are familiar with what a turing machine is, you can skip directly to the "Screenshots and How to Use" section
to familiarize yourself with the software.

Alan Turing in his 1936 research paper, "On Computable Numbers, with an Application to the Entscheidungsproblem" defined the concept of what is now known as a "Turing Machine". Turing's paper majorly dealt with the "computability" of a number, and aiming to find whether the Entscheidungsproblem is solvable.

The "computable" numbers may be described briefly as the real numbers whose expressions as a decimal are calculable by finite means.
Although the subject of this paper is ostensibly the computable numbers. It is almost equally easy to define and investigate
computable functions of an integral variable or a real or computable variable, computable
predicates, and so forth. The fundamental problems involved are, however, the same in each case, and I have chosen the
computable numbers for explicit treatment as involving the least cumbrous technique. I hope shortly to give an account
of the relations of the computable numbers, functions, and so forth to one another.
This will include a development of the theory of functions of a real variable expressed in terms of computable numbers.
According to my definition, a number is computable if its decimal can be written down by a machine.


- Alan Turing, "On Computable Numbers, with an Application to the Entscheidungsproblem" 

The Entscheidungsproblem, or "decision problem," asked if there was a systematic way to determine the truth of any given statement in first-order logic. An example of an Entscheidungsproblem-style question in the realm of mathematics could be about determining the solvability of Diophantine equations. A Diophantine equation is a polynomial equation, usually with two or more unknowns, for which only integer solutions are sought. The problem can be framed as: "Given any Diophantine equation, is there a systematic way (an algorithm) to decide whether or not the equation has an integer solution, without directly solving it?"

Alan Turing addressed this question through his conceptualization of the Turing Machine, a theoretical model for computation. Turing introduced the idea of computable numbers and functions, essentially defining what problems are solvable through algorithms. He connected this to the Entscheidungsproblem by demonstrating the Halting Problem, which asks whether it's possible to predict if a Turing Machine will stop or run indefinitely for any given input. Turing proved that such prediction is impossible because there is no universal algorithm that can determine the behavior of every Turing Machine.

This impossibility of solving the Halting Problem implies that the Entscheidungsproblem is also unsolvable. There cannot be a universal method to decide the truth or falsehood of every statement in first-order logic. Turing's findings laid foundational concepts in computability and showed the limits of what algorithms can solve, significantly impacting mathematics and computer science.

Brief on the Design and Operation of Turing Machines:

Important

The first 6-7 pages of Alan Turing's research paper introduce the concepts of computability, alongside the basic construction and operation of an elementary Turing Machine. Check out the original 36 page paper here. On page number 4, the Turing Machine represented via table has a single incorrect entry due to a misprint, the final m-config for entry 2, initial m-config c should be e, not c.

Definition

A Turing machine is a finite automaton that can read, write, and erase symbols on an infinitely long tape. The tape is divided into squares, and each square contains a symbol. The Turing machine can only read one symbol at a time, and it uses a set of rules (the transition function) to determine its next action based on the current state and the symbol it is reading.

Definitions for a Turing Machine:

Machine Configurations (M-Configs): These represent the different states of the Turing machine. Each M-Config defines the current state of the machine.

Scanned Symbols: These are the symbols read by the Turing machine from the tape at any given step.

Actions: These actions determine what the Turing machine does based on the current M-Config and the scanned symbol. Actions can include writing a new symbol on the tape (represented as P followed by the symbol), moving the tape head left (L) or right (R), erasing a symbol (E), or transitioning to a new M-Config.

New M-Config: After performing the actions based on the scanned symbol and current M-Config, the Turing machine transitions to a new M-Config, representing its updated state.

Operation of a Turing Machine:

Initial Configuration: The Turing machine starts in an initial M-Config with the tape containing an initial sequence of symbols.

Processing: At each step, the Turing machine reads the symbol currently under the tape head (the scanned symbol). Based on the combination of the current M-Config and the scanned symbol, it performs specific actions, such as writing a new symbol, moving the tape head left or right, erasing a symbol, or transitioning to a new M-Config.

New Configuration: After processing each symbol, the Turing machine reaches a new M-Config, indicating the completion of one iteration. The current m-configuration is now assigned the value of this new m-config,and computations can continue as long as long there exists a pair of actions and new m-config for the combination of the current m-config and scanned symbol.

Example Table for a Turing Machine:

Consider a simple example of a Turing machine that prints the sequence 101010..... Here's the transition table representing its behaviour:

Modern Mathematical Representation:

While Turing primarily used tables to represent his machines in the original 1936 research paper, a more concise representation involves defining it as a quintuple (Q, Σ, Γ, δ, q0, qaccept, qreject) as is more widely accepted nowadays. It comprises of:

• a finite set of states Q
• a finite set of tape symbols Σ
• a finite set of tape alphabet symbols Γ (including a blank symbol)
• a transition function δ that maps combinations of current state and scanned symbol to actions (including reading, writing, moving left or right, and transitioning to a new state)
• an initial state q0
• and accepting (qaccept)
• rejecting (qreject) states.

UML:

Purpose:

This project aims to create a windows desktop application,mobile app and web-app built with flutter which allow users to create their own turing machines, by filling in a table which contains the Configuration and Behaviour attributes. Users can then view the tape while controlling the progression of the machine's state. This application is useful to simulate and store Turing Machines encountered in Alan Turing's 1936 reserach paper as it is easier to understand the machines and follow along with this application rather than if you simulated them manually. To save machines, a secure NoSQL database, Hive was used. The logic for the project is available in the lib/models/ folder. You can find the apk/exe file in the releases section. There is also a web deployment

Screenshots and How to Use:

Note

The project overall, and especially the UI is under development and subject to constant improvement and modification, the following screenshots are representative only of the current state of the application. Please also note that the screenshots of each screen PRECEDES the description of the screen itself.

Welcome Screen:

• This screen presents the user with the option to create a machine from scratch, create a default machine, or load a saved machine.

• The default machine looks like this:

  
  

and simply populates the tape with 0's.

• Selecting the "Create Machine" or "Default Machine" option will send the user to the Table Screen with a blank table or the default table respectively.
• Selecting the "Load Machine" option will navigate the application to the Load Machine Screen.

Load Machine Screen:

• Pick one machine from the list of saved machines and click it to proceed. The machine will be loaded and presented on the Table Screen.
• You can delete a saved machine by clicking on the delete icon in the machine's name tile.
• The reset icon in the top right will delete ALL saved machines.

This screen also provides the user with the option to import machines from encoded JSON strings(which can be generated on the Table Screen).

Importing Machines:

• Turing Machines can be imported and exported as encoded JSON strings, which allows users to share machines across devices.
• To import a machine, click on the 'import/export' icon button on the top-right corner of the 'Load Machine' screen, and paste the machine export JSON string.

Table Screen:

Note

You can save a machine by clicking on the save icon in the top-right. You will get a prompt asking for a name with which the machine can be saved, an empty string is also a valid input. Ensure that the name is not already taken before saving since if there is another machine saved with the same name, it will simply get overwritten with the one being saved. Note also that only the machine description, machine table and initial configuration are saved. The machine's state on running it through X iterations will not be saved. Any changes made to the machine after it is saved with a name must ALSO be saved before quitting out if you want the changes to persist. The application does NOT autosave anything at any point. Additionally, users can add a description for their machines by tapping the info Icon Button on the top-right, then editing and saving the text which appears in the description prompt.

• The Table on this screen represents the Turing Machine's behaviour. It consists of the following columns: M-config, Symbol, Actions, New m-config.
• Each entry in this table, therefore can be read as: While the machine is in [M-config] and the tape-head is reading symbol [Symbol], execute [Actions] and switch into [New m- config].
• The table initially displays a sample turing machine which continuously prints 0's and moves the tape head right. You can reset the entire machine and start afresh with the restart icon button in the top-right. This erases and resets the tape and deletes the table.
• You can add new entries by inputting m-config,symbol scanned,actions and final m-config into the labelled textFields and clicking on the "Add Row" button.
• You can select a particular entry you want to delete via selecting it in the associated drop-down and clicking on the delete button.
• You can select an initial m-config via it's associated dropdown.
• Grammar-Parsing: If you want to check for the correctness of a certain input with respect to the grammar defined by the turing-machine created, you can input an initial tape string via it's associated text-field located at the bottom of the screen. Once the string is inputted, click on the "Print onto Tape" button to apply the change. Note that while this resets the tape pointer to 0 and makes it so that the tape is initially only as big as the input provided(each character populates one tape-cell), it will not reset the current m-config to the initial m-config.
• Once you are satisfied with your changes, click on the "Create/Resume Machine" button.

Important

There are 2 special symbols: ANY and NONE.
ANY is a wildcard and will match every symbol. NONE represents a blank cell ("").
If there are multiple entries for a particular m-config for different scanned symbols, and you want to specify an "ANY" case, all other symbols are checked before "ANY",this entry will only be considered if there are no other pairs of {m_config,scanned symbol} which match the current Configuration of the machine.
These two special symbols are not case-sensitive.

Actions:

• There are four valid actions: P(Print), R(Move tape head right), L(Move Tape head left), E(Erase current symbol).
• An example of a valid Actions String is: P1,R,R,E ->Print 1, Move Right,Move Right, Erase symbol at head pointer.
• Actions are case-sensitive.

Exporting Machines:

• This screen also provides the facility to export turing machines as JSON strings which you can import on the Load Machine Screen.
• Click on the 'share' icon on the top-right.
• This displays the encoded JSON string representation of the machine. Copy this string and share it with your friends.

Tape-Screen:

• The Tape here represents the tape of the turing machine constructed in the previous screen.

• This page is meant for controlling and observing how the turing-machine progresses and does not have features to edit the configuration of the machine.

• Progress the turing machine by clicking the Floating Action play button in the bottom right region.

• You can hard-reset the tape by clicking on the restart icon-button in the top-left region: This will erase all symbols on the tape, and reset the pointer to 0, even changing the m-config to the initial m-config specified in the previous screen.

• You can navigated between the Tape and Table Screen via the back button- any changes you make to the machine in The Table Screen will apply when you navigate back to the Tape Screen. Navigating back and forth between these two screens will not reset the tape, unless you explicitly reset the tape or the entire machine itself via the associated Icon Buttons.

  Automating Progression

  • The progress of the turing machine can be automated on the tape screen via the 'Automate Progression' checkbox. This will make the turing machine advance through m-configs automatically, without user input- until it either halts, or the user disables automatic progression.
  • All controls on the screen are disabled during automatic progression to prevent inconsistent behaviour.
  • The time gap between each automatic iteration is 1000 milliseconds by default, but can be changed by clicking on the clock icon on the top-right. Please note that this gap also applies to the 0th automatic iteration.
  
  

  For any issues with the project, please either open an issue or contact me via e-mail: javakingxi@gmail.com

Special Mentions:

• Chandrama Saha: While Chandrama has not helped with the technical aspects of the project, she has supported me through my journey as a developer and motivated me to keep learning, buidling and breaking software. She has also worked on the final version of the improved UI(not implemented yet). Most projects I build with flutter implement her fantastic designs.
• Anshul: Anshul helped me debug my "ANY" symbol and has helped me improve the efficiency of the application on multiple occasions. He has provided me with the support and kind words required to see my work through on multiple occasions. Anshul has also acted as an external tester for this project.