The shape of the learned relation. The 256 byte values are ticks on one baseline in byte order. Every k=1 rule is an arc from its source tick to its successor tick, above the line for a forward step in byte order and below for a backward one. Every arc is the same hairline: support is arc height and nothing else, so this page has exactly one visual variable and height can be read off it as one quantity. Nothing is selectable and nothing moves.
12 forward arcs above, 244 backward below. Under B1 every arc is the same height, because the file stores no k=1 weight at all — the height here is the stated constant 8. Put the B2 page beside it and the skyline appears.
| read for | what it is, and where |
|---|---|
| hubs | ticks many arcs land on. Here: 00 (229 arcs in), / (3 arcs in), " (2 arcs in), . (2 arcs in), m (2 arcs in), i (2 arcs in). These are the bytes the model expects after most things, and they are why a window can settle to one answer from several directions. |
| short arcs | the alphabet's local runs — a letter naming a neighbouring letter. They sit low and tight against the baseline near the printable range. |
| long arcs | rules that cross the whole range, into punctuation and the high bytes. A long arc from a high byte is usually a byte that never occurs in the sample: the argmax table has an entry for every byte value whether or not it was ever seen. |
| cycles | 1 pairs whose arcs mirror each other above and below the line: i↔k. These are exactly the positions where settling can oscillate rather than converge — each byte names the other, so a forward application and a backward one can push a position back and forth forever. That is what the conv column of gen5.tsv is about when it reads W. |
A second, fainter baseline whose ticks are the 65536 two-byte contexts in lexicographic order. An arc runs from the context a rule fires in, (a, b), to the context the step lands in, (b, c) — the same construction as above, one order up, so the two orders of the model can be compared as two skylines without either being aggregated into the other. 47 rules are kept; 65536 − 47 contexts carry none.
The k=2 rules DO carry their strength in the file, under B1 and B2 alike, so this skyline is the same on both pages. Where it clusters is where the sample's two-byte contexts are: the printable band, and nowhere else.
#hutter_metrics).Published under #viz_standard. Self-contained: no external stylesheet, no font, no image, nothing fetched. Built from the spec in p8v2-pattern-viz-specs.md by docs/pprog/build-p8v2-patterns, never hand-edited. Every pattern drawn was reconstructed through the query layer from (program text, model file); no page reads a de-optimized dump. Nothing here is a result and no page carries a chart point — the picks are the programmer's (#variant_protocol).