Commands › › Network Break And Offset45 Down On Selection
Network Break And Offset45 Down On Selection
Coming soon
Before you run this
Active document must be open. At least one pipe selected in the UI.
After it runs
Selected pipes are broken and re-joined through a 45° down-ramp of the requested ΔZ.
When to use this
- User needs to dodge a clash by stepping a run down-and-under.
Don't use this when
Rectangular-duct offsets (need a separate fitting-lookup strategy).
Decision flow
1) Pull selection → require ≥1 Pipe. 2) Resolve ΔZ (resolver, default 150 mm). 3) For each pipe: compute plan via GetBreakAndOffsetGeometry. 4) Open Transaction "Break & Offset 45° Down". 5) Apply each plan via ApplyBreakAndOffsetToPipe. 6) Commit, report counts. 7) Failure → ErrorManager.WireFault + CentralWarningLogger.LogError.
What you'll see in the chat
on start
Running NetworkBreakAndOffset45DownOnSelectionCommand...
thinking
Validating selection...
Computing 45° down ramp geometry...
Applying ramps inside transaction...
Computing 45° down ramp geometry...
Applying ramps inside transaction...
on success
NetworkBreakAndOffset45DownOnSelectionCommand completed successfully.
on failure
NetworkBreakAndOffset45DownOnSelectionCommand 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_offset45_down_on_selection- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
networkbreakandoffset45downonselection
Related
| Pillar |
|---|