Commands  ›  Clash Manager / Solver  ›  Clash Solver Extend Selected Node By100mm

Clash Solver Extend Selected Node By100mm

Clash Manager / Solver writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; element + connector id resolvable; connector is not already connected.

After it runs

Exactly one new Pipe created inside one Transaction.

When to use this

Don't use this when

Extending every connector at once — use the other Extend* command.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) element unique id + connector id required.
2) Resolve element + ConnectorManager; fetch the connector by Id; WireError if any missing.
3) If connector.IsConnected → WireRecoverable + no-op + tracker output says already_connected.
4) length_mm = length mm ?? 100; direction = connector.CoordinateSystem.BasisZ.
5) Resolve PipeTypeId + SystemTypeId + LevelId from the source element / connector.
6) Open Transaction "ClashSolver::ExtendNode"; Pipe.Create(doc, systemTypeId, pipeTypeId, levelId, origin, origin + dir*length); set diameter from connector; commit.
7) Emit created_pipe_id, length_mm, origin_ft, direction.

What you'll see in the chat

on start
Extending one named connector by 100 mm…
thinking
Resolving element + connector id…
Creating a single Pipe along the connector axis…
on success
Created pipe {pipe_id} ({length_mm} mm) from connector {connectorId}.
on failure
Extend-node 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/clash_solver_extend_selected_node_by100mm
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolverextendselectednodeby100mm · extend node · extend single connector

PillarClash Manager / Solver