The stage atom's run #
The run theorem of DescriptiveComplexity.Draw.Data.stageRule – the
random access. The tuple loops stay abstract (one hypothesis for the whole
chain, discharged by DescriptiveComplexity.Draw.tuple_run at
instantiation); this file contributes the itinerary around them: save the
mirror, clear the target, run the loops, reset, clear the mirror, seek the
target, read the stage bit under the head, restore the target, and come
home the same way.
The statement is in the DescriptiveComplexity.Draw.TapeSt idiom: the
machine's mutable state is a record, each leg one update, and every slot
equation a kit asks for is definitional in
DescriptiveComplexity.Draw.Data.ixBack; the handoff between legs walking
different tracks is DescriptiveComplexity.Draw.Data.trackTape_back_gen.
The file is a parameter. A clocked program has no register per element, so
the run is stated at an arbitrary DescriptiveComplexity.Draw.LaidFile with the
address correspondence of DescriptiveComplexity.Problems.Wide.IxAddr: what the
mirror, the save and the target hold are the marks of their addresses
(DescriptiveComplexity.ixMark), and the seek's verdict is again an equality of
addresses because the correspondence carries the order. The elementwise file is
that at the identity (DescriptiveComplexity.Draw.Data.diagLaid), which is
what stageAtSt, stageEndSt and trackTape_back_gen_diag are.
The state at the far end of the random access: marker and mirror on the target, the mirror's address saved, the target built.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The state the random access returns in: the target and the save both holding the home address, everything else as at entry.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
A leg's after-tape, read against the state it produced: the walked
track moves into the new state's background, whose other slots agree with
the old one's. The generic sibling of the concrete
DescriptiveComplexity.Draw.Data.trackTape_back.
Dependency graph
The stage atom's run, on a clock: from its entry phase one cell to the
right of the marker – save, clear, the loops, the reset–clear–seek out, the
read under the head, the restore, and the reset–clear–seek home – to the exit
phase, the verdict setAv b in the control and the marker, mirror and save
restored at the home address. Five passes of the file, two resets, two seeks,
the loops, and the thirteen dispatches between them.
Dependency graph
The stage atom's run, the budget forgotten: what a space-bounded caller reads. The width of a trip is then the largest of the finitely many the atom takes.
Dependency graph
The chain of the copy loops #
The k tuple loops run head to tail – position ℓ's exit is
DescriptiveComplexity.Draw.Data.stageNextTup emb ℓ – so their chain is
one induction over the positions, each round an abstract per-position run
(discharged by the copy loop's instantiation) between the walk-backs this
file's rules provide.
The phase before the n-th copy loop – the first reset's checkpoint
once the positions are exhausted.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The copy loops, chained, on a clock: from the phase entering the first loop – one cell to the marker's right, as every dispatch leaves it – to the first reset's checkpoint, each position's run handed to the next by its own walk-back, and one walk-back and one loop paid per position.
Dependency graph
The copy loops, chained, the budget forgotten: from the phase entering the first loop – one cell to the marker's right, as every dispatch leaves it – to the first reset's checkpoint, each position's run handed to the next by its own walk-back.
Dependency graph
The elementwise instantiation #
The space-bounded program's file is the input channel's ruler, one register per element: the runs above are that file at the identity embedding, and these are the statements their callers had before the file became a parameter.
The far state of the random access at the elementwise file.
Equations
- DescriptiveComplexity.Draw.Data.stageAtSt st v mT = dt.ixStageAtSt st id v mT
Instances For
Dependency graph
The state the random access returns in, at the elementwise file.
Equations
- DescriptiveComplexity.Draw.Data.stageEndSt st v = dt.ixStageEndSt st id v
Instances For
Dependency graph
A leg's after-tape at the elementwise file.