Commands  ›   ›  Connector Ops Connect Into Nearest Node In3d

Connector Ops Connect Into Nearest Node In3d

writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; source element + connector resolvable; at least one candidate connector within radius.

After it runs

Exactly one Connector.ConnectTo call inside one Transaction; no other mutation.

When to use this

Don't use this when

Bulk connection — use it per end.

Decision flow

1) Resolve source: element unique id required. If connector id given, use it; else pick the single unconnected connector (WireError if 0 or multiple).
2) Build candidate pool: every element with a ConnectorManager in the doc, every connector on those, filtered to same Domain + IsConnected=false + not on source element, within MaxSearchRadiusMm.
3) For each candidate, call MatchSystemByName.Evaluate. Drop Abort decisions. Keep Proceed directly; keep ProceedWithWarning only if allow cross system with warning == true.
4) Rank by source→candidate Euclidean distance (feet). If empty, WireError "no_candidate".
5) Open Transaction "ConnectorOps::ConnectNearest3d"; source.ConnectTo(nearest); commit. WireRecoverable + RollBack on API throw.
6) Emit connected, target_element_id, target_connector_id, distance_mm, match_decision, reason.

What you'll see in the chat

on start
Searching for nearest compatible connector…
thinking
Resolving source connector…
Scanning candidate pool within radius…
Filtering via MatchSystemByName…
Ranking by distance; calling Connector.ConnectTo…
on success
Connected to element {target_element_id} / connector {target_connector_id} at {distance_mm} mm.
on failure
Connect-nearest (3D) 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/connector_ops_connect_into_nearest_node_in3d
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

connectoropsconnectintonearestnodein3d · connect into nearest node 3d · clash solver connect

Pillar