Commands  ›   ›  Voxel Grid Route Pipe Or Duct Between Connectors

Voxel Grid Route Pipe Or Duct Between Connectors

writes to model Public API · not yet exposed

Coming soon

Before you run this

Voxel grid cached for scope; start/end points reachable; system + type + level resolvable.

After it runs

One or more placeholder pipe/duct segments inside one Transaction.

When to use this

Don't use this when

Multi-service rack — use RouteMultiServiceRack.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "voxel_routing" Deterministic config preset

Decision flow

1) Resolve cached grid from scope_tag. WireError if not cached.
2) Snap start/end to cells.
3) Run A* (allow_45).
4) If not found → WireError + emit reason.
5) Open Transaction; emit pipe or duct placeholders via service; commit.
6) Emit placeholder ids + cost + path length.

What you'll see in the chat

on start
Voxel-routing pipe/duct…
thinking
Running A*…
Emitting placeholders…
on success
Routed {placeholder_count} placeholders.
on failure
Route 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/voxel_grid_route_pipe_or_duct_between_connectors
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

voxelgridroutepipeorductbetweenconnectors · voxel route pipe · voxel route duct

Pillar