fix: a long two-fibre span is a cable run, not a drop cable #11

Merged
jaylouisw merged 1 commit from fix/drop-cable-span into main 2026-11-17 21:32:32 +00:00
Owner

What this changes

Fixes #10. A two-fibre span 1.2 km long was designed on g657a2-drop-2 — drop cable — because
cableFor returns 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):

span cable
≤ 300 m, 1 fibre g657a2-drop-1
≤ 300 m, 2 fibres g657a2-drop-2
> 300 m, any count ladder, 12-fibre floor

DROP_CABLE_MAX_M is exported so the threshold is a named constant rather than a magic number in two
builders.

How it was verified

npm test    # 17 suites, 157 assertions, 0 failed
  • unit: cableForSpan(2, 1200).fiberCount >= 12, cableForSpan(2, 120) is drop-2,
    cableForSpan(1, 50) is drop-1 — both sides of the boundary;
  • design: two points 1.2 km apart, assert no non-drop span over 300 m is below 12 fibres;
  • the existing taper test now checks the length rule as well as the fibre count.

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

## What this changes Fixes #10. A two-fibre span 1.2 km long was designed on `g657a2-drop-2` — drop cable — because `cableFor` returns 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)`: | span | cable | |---|---| | ≤ 300 m, 1 fibre | `g657a2-drop-1` | | ≤ 300 m, 2 fibres | `g657a2-drop-2` | | > 300 m, any count | ladder, 12-fibre floor | `DROP_CABLE_MAX_M` is exported so the threshold is a named constant rather than a magic number in two builders. ## How it was verified ``` npm test # 17 suites, 157 assertions, 0 failed ``` - unit: `cableForSpan(2, 1200).fiberCount >= 12`, `cableForSpan(2, 120)` is drop-2, `cableForSpan(1, 50)` is drop-1 — both sides of the boundary; - design: two points 1.2 km apart, assert no non-drop span over 300 m is below 12 fibres; - the existing taper test now checks the length rule as well as the fibre count. 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
fix: a long two-fibre span is a cable run, not a drop cable
All checks were successful
CI / Test (Node 18) (pull_request) Successful in 42s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Server smoke test (pull_request) Successful in 53s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Docker build (pull_request) Successful in 1m15s
3b326aa1e1
cableFor picks the smallest cable that carries the fibre count, so a two-fibre span of 1.2 km came
out as g657a2-drop-2 - drop cable, which is short tight-buffer cable for a run into a property and
not something anyone pulls between buildings. The old home-run builder had a length rule; the
street-routing refactor put every span through one cable choice and lost it.

cableForSpan now decides by length as well as fibre count: at or under DROP_CABLE_MAX_M (300 m) a
two-fibre run keeps drop-2 and a one-fibre run keeps drop-1; anything longer goes to the ladder with
a 12-fibre floor.

Found while probing a DC-to-DC link - the case that made it visible, since that is a long two-fibre
run by nature. The design-level test asserts no long non-drop span is below 12 fibres, and the unit
test pins both sides of the 300 m boundary.

Closes #10
jaylouisw deleted branch fix/drop-cable-span 2026-11-17 21:32:34 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/glassforge!11
No description provided.