fix: a long two-fibre span is a cable run, not a drop cable #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/drop-cable-span"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What this changes
Fixes #10. A two-fibre span 1.2 km long was designed on
g657a2-drop-2— drop cable — becausecableForreturns the smallest cable that carries the fibre count, and drop cable is two-fibre.Drop cable is short, flat, tight-buffer cable for the run into a property. Nobody pulls it between
buildings or between data centres. The old home-run builder had a length rule; the street-routing
refactor routed every span through one cable choice and lost it.
The rule now
cableForSpan(fibres, lengthM, ladder, registry):g657a2-drop-1g657a2-drop-2DROP_CABLE_MAX_Mis exported so the threshold is a named constant rather than a magic number in twobuilders.
How it was verified
cableForSpan(2, 1200).fiberCount >= 12,cableForSpan(2, 120)is drop-2,cableForSpan(1, 50)is drop-1 — both sides of the boundary;Found while probing a DC-to-DC link, which is a long two-fibre run by nature — that is the case where
the wrong cable was most visible.
Closes #10