Research notes on every problem, and a library of the papers behind them. Built from the open erdos repository.
Updated
Source. Section 2, physical pp. 1–4 of the selected author version. The formulation below makes explicit the recursive semantics used by the paper's diagrams.
Expressions and targets
An expression denotes a family of global residue classes. Only congruence conditions explicitly present on a root-to-leaf path contribute to the modulus of an output class. A target or hole is a set that the union of those classes is intended to contain; the congruence conditions defining the target are not silently intersected into every output class.
This distinction is essential. On the modulus- and modulus- target branches, the first input of the prime- template produces moduli , not or . Its classes are larger than the target pieces but still contain them. The prime- stage likewise uses classes that intentionally cover beyond the immediate target.
Nodes and children
At an explicit node of a -tree, the current syntax has fixed a -coordinate . Its children are the compatible classes modulo , ordered by increasing least positive representative in that -coordinate. Suppose packages are placed in the respective children. Then
means: intersect every class in with the explicit th child condition and with the explicit ancestor conditions on the syntax path. A blank contributes no class. An atomic takes the child itself. More generally, an integer records the compatible residue condition of modulus . The modulus of a resulting class is the least common multiple of the explicitly imposed moduli. In the regular uses here, factors are coprime or successive powers of one prime, so the modulus is read by multiplying the displayed new prime factors.
For example, selects the third class modulo . The expression selects one class modulo , and is one class modulo . The latter class may be used to cover part of a narrower target, but no further target modulus is added.
The sign unions packages. An marks a child already covered by another summand and contributes no new class. Suppressing parentheses, as in , means that both displayed compatible conditions are explicitly imposed. Thus their factors do enter the modulus.
Relative coverage
For a target set , write for its intersection with the th explicit child of a node. The recursive coverage rules are:
- the are pairwise disjoint and have union ;
- a package is valid in input when the union of its explicit classes contains , even if those classes also contain points outside ;
- the node covers once every is covered, possibly by unions of several packages; and
- an is valid only when the corresponding target piece was already covered.
This is exactly what black, gray, and white nodes record in the source: black means the relevant target piece is covered, gray means partial coverage, and white means an unresolved target piece. It is a relative coverage claim, not a statement that every output class is contained in the target.
Arrows and selected-input tails
The symbol repeats the displayed regular inputs at every higher -level and retains the th child as the marked continuation. Its precise finite meaning is given on the arrow page.
If one displayed input is deleted, its regular class is missing at every level. The source sometimes restores all but the first of those missing classes by a contextually selected package . This is the arrow portion of the selected input: it covers that input's copies at levels , while its first -level class remains a hole. It is distinct from the outer arrow's th marked continuation. This convention is used for the deleted prime- inputs and the one empty prime- input.
Modulus signatures
For collision checking, attach to every explicit regular leaf the vector
Two positive moduli are equal exactly when these vectors agree. An unrelated target condition never appears in . Adding a new explicit outer prime appends a positive -coordinate; moving to a different level of the same -tree changes that coordinate. At one fixed level, the input packages must already have disjoint signature sets. Neither changing residues nor choosing a later arrow cutoff can repair a duplicate regular signature.
The exact ordered input maps and their signature checks are recorded in the template pages and the construction ledger.
Bears on. Problem 2.