Commands  ›   ›  Connector Ops Connect Into Nearest Node In2d

Connector Ops Connect Into Nearest Node In2d

writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; source element + connector resolvable; at least one candidate within 2D radius at the same Z.

After it runs

Either a direct Connector.ConnectTo or a doc.Create.NewElbowFitting inside one Transaction.

When to use this

Don't use this when

3D routing — use the 3D variant.

Decision flow

1) Resolve source connector (same rule as 3D).
2) Candidate pool restricted to |Δz| ≤ z tolerance mm; 2D distance ≤ max search radius mm.
3) System-match gate.
4) Rank by 2D distance.
5) Transaction "ConnectorOps::ConnectNearest2d"; try source.ConnectTo(pick).
   If that leaves IsConnected=false, try doc.Create.NewElbowFitting(source, pick). Commit on success.
6) Emit result + used_fitting flag.

What you'll see in the chat

on start
Searching for nearest compatible connector on plan…
thinking
Restricting candidates to the same Z level…
Calling Connector.ConnectTo; falling back to NewElbowFitting if needed…
on success
Connected in 2D at {distance_mm} mm (fitting={used_fitting}).
on failure
Connect-nearest (2D) 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_in2d
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

connectoropsconnectintonearestnodein2d · connect into nearest node 2d · plan-view connect

Pillar