Auto-design: topology synthesis from a list of addresses #6

Closed
opened 2026-11-17 09:01:33 +00:00 by jaylouisw · 0 comments
Owner

Glassforge plans a PON. It cannot plan an active optical network, and it cannot design one:
the user supplies neighbours and a head-end, and the planner works out the topology and the runs.

Ask

Input a list of addresses (or coordinates) plus the head-end site, and have Glassforge:

  1. choose the topology that fits — PON with splitters, active Ethernet home-run, or active Ethernet
    over a shared cable tree with closures;
  2. lay out the runs: which cable model, how long, and what it feeds;
  3. reject a candidate that does not meet its own optical budget, and say why;
  4. rank the survivors and explain the winner in one sentence a reviewer can check.

Acceptance

  • POST /api/design/synthesise takes demand points, a head-end and options, and returns every
    candidate with its metrics, the winner, the plant it built (valid under network.validate), the
    per-ONT budget and the bill of materials.
  • The same input always produces the same output (no Math.random, deterministic tie-breaks).
  • Active links are budgeted against transceiver parts, not against a PON class — a new
    transceiver kind (launch power, sensitivity, overload, reach) with budget.pointToPoint.
  • A candidate that needs more PON ports than the OLT has, or a run longer than the transceiver
    reaches, is marked infeasible with that reason — never silently dropped from the comparison.
  • Addresses without coordinates are refused by name: geocoding is off by default (no outbound
    requests), so the message has to say "supply lat/lon" rather than "invalid input".
  • The UI exposes it: paste the list, pick a technology, see the comparison, apply the winner to the
    open project.

Not in this issue

Street-graph routing. v0 measures straight line × a stated detour factor (routeFactor, default
1.2) and says so in every result; routing along an imported duct/street network is its own issue.

Glassforge plans a PON. It cannot plan an **active optical** network, and it cannot design one: the user supplies neighbours and a head-end, and the planner works out the topology and the runs. ## Ask Input a list of addresses (or coordinates) plus the head-end site, and have Glassforge: 1. choose the topology that fits — PON with splitters, active Ethernet home-run, or active Ethernet over a shared cable tree with closures; 2. lay out the runs: which cable model, how long, and what it feeds; 3. reject a candidate that does not meet its own optical budget, and say why; 4. rank the survivors and explain the winner in one sentence a reviewer can check. ## Acceptance - `POST /api/design/synthesise` takes demand points, a head-end and options, and returns every candidate with its metrics, the winner, the plant it built (valid under `network.validate`), the per-ONT budget and the bill of materials. - The same input always produces the same output (no `Math.random`, deterministic tie-breaks). - Active links are budgeted against **transceiver parts**, not against a PON class — a new `transceiver` kind (launch power, sensitivity, overload, reach) with `budget.pointToPoint`. - A candidate that needs more PON ports than the OLT has, or a run longer than the transceiver reaches, is marked infeasible with that reason — never silently dropped from the comparison. - Addresses without coordinates are refused by name: geocoding is off by default (no outbound requests), so the message has to say "supply lat/lon" rather than "invalid input". - The UI exposes it: paste the list, pick a technology, see the comparison, apply the winner to the open project. ## Not in this issue Street-graph routing. v0 measures straight line × a stated detour factor (`routeFactor`, default 1.2) and says so in every result; routing along an imported duct/street network is its own issue.
Sign in to join this conversation.
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#6
No description provided.