Active optical networks and auto-design from an address list #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/auto-design"
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
Adds active optical networks and an auto-design engine, which is what issue #6 asks for: a list of
addresses plus a head-end in, a sized topology and its runs out.
transceiverpart kind — 5 optics (1000BASE-LX/ZX, 10GBASE-LR/ER, 25GBASE-LR) with launchpower, sensitivity, overload, wavelength, reach.
budget.pointToPoint— an active link budgeted against the optic pair'slaunch − sensitivityinstead of a PON class, with a separate reach check. The passive-loss maths is now shared with the
PON path (
computeOdn) so the two definitions cannot drift.headendnode type — an active plant's root.trace,validate,capacityanddesignForOntkey off the root's technology.engine/demand.js— CSV/JSON demand with per-row rejection, dedupe, and no empty-cell→0 trap.engine/design.js— PON per splitter ratio, active-over-a-tree, active home-run; validated,budgeted per ONT, costed, ranked, every rejection explained.
POST /api/design/synthesise(with one-undoapplyToProject),POST /api/import/demand, and an Auto-design panel that shows the comparison and applies the winner.Why the objective is fibre-metres
Cable is priced roughly with its fibre count. Ranking by plain metres made a fat tree look cheap and
picked the wrong topology on any street longer than a few hundred metres.
fibreMetresis the defaultmetric,
cableMis reported alongside it, and acostsmodel switches the objective to money — andthe response says which objective it used.
Three defects the feature exposed (fixed here)
capacity()multiplied the ratio of every splitter in the plant, so six 1:8 sites read as1:262144 and refused a good PON design. It now walks the tree and takes the deepest single path.
cableForreturned the first cable in the (richest-first) ladder that fit, so every two-fibrebranch was designed on 144-fibre cable.
third site. Each splitter site now has its own closure with the splitter on a 1 m tail.
How it was verified
Plus the real UI driven end to end in a browser: 24 addresses pasted, comparison rendered
("pon wins: 26987.7 fibre-metres"), applied to the project → 49 nodes / 48 spans, validation clean,
capacity
24 / 1024 ONTs, cascade 1:8.A worked comparison on a 2 km street of 40 houses:
What it deliberately does not do
Street/duct routing (straight-line ×
routeFactor, stated in every response — issue #7), geocoding(no outbound requests), and active-equipment sizing (an active plant reports
ports: nullrather thaninventing a ceiling).
Checklist
node scripts/count-parts.js) — 37 parts across 8 kindsnpm testgreen locally on Node 24; CI will confirm 18/20/22Closes #6