Resetting the working cell to the bottom #
A random access starts at the checkpoint: marker and mirror at the empty
address. Getting there from wherever the marker is –
DescriptiveComplexity.Draw.Prog.reaches_reset – is the one itinerary of the
program that runs down the working area: erase the marker and step
right (never left, so the empty address needs no special case), scan left
to the cell the permanent bot mark identifies, write the marker there
stepping right, and bounce back left onto it. The mirror is cleared by a
separate DescriptiveComplexity.Draw.ClearKit trip afterwards.
DescriptiveComplexity.Draw.ResetKit is the kit: the scan and the two
bounce steps; the erasing entry is the caller's rule, and the landing phase
hosts nothing – the machine arrives exactly once, at the bottom cell, where
the caller's exit fires.
The reset, on a clock: from the caller's phase at the marker – whose
erasing step, rightwards, is the caller's rule – scan left to the bottom cell,
write the marker there stepping right, and bounce back onto it. The empty
address is identified by the permanent bot mark, and no leftward step is ever
taken at it. The scan is a walk down the whole order below the marker, so the
cost is the marker's rank and the three steps around it.
Dependency graph
The reset, the budget forgotten.
Dependency graph
The reset kit #
The phases of a reset: the down-scan, the bounce, and the landing – which hosts no rule, the caller's exit firing on arrival.
- scan : ResetPh
Scanning left to the bottom cell.
- b : ResetPh
The marker written, bouncing back.
- done : ResetPh
At the bottom cell, marker set.
Instances For
Dependency graph
Dependency graph
Dependency graph
The rule families of a reset.
- down : ResetRule
Scan left while the bottom mark is clear.
- put : ResetRule
At the bottom cell: write the marker, step right.
- back : ResetRule
Bounce back left onto the marker.
Instances For
Dependency graph
Dependency graph
Dependency graph
A reset kit: the walked track, the bottom-mark and marker slots, and the phases.
- t : W
The walked track (rides along unchanged).
- bt : W
The bottom mark, planted at the empty address at startup.
- wk : W
The working-cell marker slot.
- emb : ResetPh → P
The kit's phases in the program.
Instances For
Dependency graph
The kit's rules.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
A reset stays inside its own phases: every rule of the kit lands in one of the three the kit was given.
Dependency graph
In-shape separation.
Dependency graph
Exit disjointness at the landing phase: no kit rule fires from it at all.
Dependency graph
The kit resets the marker to the bottom, on a clock: from the caller's phase at the marker – whose erasing step is the caller's rule, the one hypothesis beyond the slot equations – to the landing phase on the empty address, down the whole order below the marker.
Dependency graph
The kit resets the marker to the bottom, the budget forgotten.
Dependency graph
Going home #
After a plain sweep the machine stands at the top of the stretch while the marker never moved: getting back is a scan, not a reset. One phase, one rule – walk left unless the marker is under the head – and the caller's exit fires on arrival.
The walk home, on a budget: from anywhere at or above the marker, scan left to it, in the difference of the two ranks. The marker's cell is identified by its own slot, and nothing on the way is rewritten.
Dependency graph
The walk home: from anywhere at or above the marker, scan left to it. The marker's cell is identified by its own slot, and nothing on the way is rewritten.
Dependency graph
A home kit: one phase, one rule – walk left unless the marker is
under the head. The caller's exit, guarded wk = one ∧ rg ≠ one, is
disjoint by construction.
- t : W
The walked track (rides along unchanged).
- wk : W
The working-cell marker slot.
- ph : P
The kit's phase in the program.
Instances For
Dependency graph
Dependency graph
Dependency graph
Dependency graph
The kit's rule.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
In-shape separation: one rule, nothing to separate.
Dependency graph
Exit disjointness: the rule never fires at the marker.
Dependency graph
The kit walks home, on a budget: from anywhere at or above the marker, down to it, in the difference of the two ranks.
Dependency graph
The kit walks home: from anywhere at or above the marker, down to it.