Rules and initial conditions (2) 

MultiwayTuringMachine accepts lists of Turing machine IDs:

In[31]:=

Out[31]=

Simulating 3-state 2-color machines:

In[32]:=

Out[32]=

MultiwayTuringMachine also accepts explicit lists of transitions:

In[33]:=

Out[33]=

MultiwayTuringMachine accepts both individual initial conditions and lists of initial conditions:

In[34]:=

Out[34]=

In[35]:=

Out[35]=

Event selection functions (2) 

Apply only the first possible event at each step:

In[36]:=

Out[36]=

Apply the first and last possible events at each step:

In[37]:=

Out[37]=

State node rendering (5) 

By default, states are labeled by their contents:

In[38]:=

Out[38]=

Use no labeling for states:

In[39]:=

Out[39]=

"StatesGraphStructure" yields the same result:

In[40]:=

Out[40]=

Use raw state names as node labels:

In[41]:=

Out[41]=

Use a named shape as each state label:

In[42]:=

Out[42]=

Event node rendering (4) 

By default, both states and events are labeled by their contents:

In[43]:=

Out[43]=

Use no labels for states or events:

In[44]:=

Out[44]=

"EvolutionEventsGraphStructure" yields an equivalent result:

In[45]:=

Out[45]=

Use raw event expressions as their labels:

In[46]:=

Out[46]=

Initialization events (3) 

By default, "AllEventsList" does not include initialization events:

In[47]:=

Out[47]=

The option "IncludeInitializationEvents" allows one to override this default:

In[48]:=

Out[48]=

Initialization events have special default rendering:

In[49]:=

Out[49]=

Graph layout options (2) 

Place arrows in the middle of edges:

In[50]:=

Out[50]=

Generate an example of multiway Turing machine evolution:

In[51]:=

Out[51]=

Force the initial state node to be at the top:

In[52]:=

Out[52]=

Step numbers and state IDs (5) 

By default, equivalent states are merged across all time steps:

In[53]:=

Out[53]=

In[54]:=

Out[54]=

Merging of equivalent states across different time steps can be prevented by including step numbers:

In[55]:=

Out[55]=

In[56]:=

Out[56]=

Merging of equivalent states at the same time step can be prevented by also including state IDs:

In[57]:=

Out[57]=

In[58]:=

Out[58]=

Step numbers and IDs also apply to events:

In[59]:=

Out[59]=

See the events:

In[60]:=

Out[60]=

Event instances (2) 

By default, multiple instances of equivalent updating events are merged in the states graph:

In[61]:=

Out[61]=

Merging of equivalent events can be prevented by including event instances:

In[62]:=

Out[62]=

State (path) weights (2) 

Vertices of a states graph can be weighted by their relative rate of occurrence at each time step:

In[63]:=

Out[63]=

Vertices can also be weighted by the number of distinct evolution paths that lead to them:

In[64]:=

Out[64]=

MaxItems (2) 

By default, "CausalGraphInstances" returns all possible causal graphs:

In[65]:=

Out[65]=

The number of causal graphs returned can be limited using MaxItems:

In[66]:=

Out[66]=

Predecessors and resolvents (2) 

By default, "BranchPairsList" returns only a list of branch pairs:

In[67]:=

Out[67]=

Common predecessor states can be shown using "GivePredecessors":

In[68]:=

Out[68]=

Similarly, "BranchPairResolutionsList" by default lists only resolved and unresolved branch pairs:

In[69]:=

Out[69]=

Common resolvents of resolved branch pairs can be shown using "GiveResolvents":

In[70]:=

Out[70]=

Show both common predecessors and common resolvents, where appropriate:

In[71]:=

Out[71]=

Full branchial space (2) 

By default, non-branch pair states are not shown as part of the branchial graph:

In[72]:=

Out[72]=

They can be shown using "IncludeFullBranchialSpace":

In[73]:=

Out[73]=