Commands  ›   ›  Network Break And Rise Group By Connected Component

Network Break And Rise Group By Connected Component

writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document. A seed pipe selected (or set via seed id).

After it runs

All parallel pipes in the seed's connected component are broken and re-routed through the chosen ramp profile in one undo step.

When to use this

Don't use this when

Mixed-system runs (graph spans systems — flagged and skipped per pipe).

Decision flow

1) Resolve seed pipe. 2) Build component via GetConnectedComponentGraphOfNetwork. 3) Enumerate MEPCurve elements; filter by bearing (± tolerance). 4) Transaction "Break & Rise (Component)". 5) For each edge: plan + apply. 6) Commit, count. 7) Failures → WireFault.

What you'll see in the chat

on start
Running NetworkBreakAndRiseGroupByConnectedComponentCommand...
thinking
Walking connected component...
Filtering parallel edges...
Applying ramps to each edge...
on success
Lifted {count} pipes across the connected component.
on failure
NetworkBreakAndRiseGroupByConnectedComponentCommand failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/network_break_and_rise_group_by_connected_component
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

networkbreakandrisegroupbyconnectedcomponent

Pillar