Commands  ›  Clash Manager / Solver  ›  Clash Solver Detect Thread Of Services And Combine Bounding Boxes

Clash Solver Detect Thread Of Services And Combine Bounding Boxes

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

Coming soon

Before you run this

Active document; input element ids (resolver or selection); each element has a BoundingBox.

After it runs

No mutation; audit records threads + unthreaded.

When to use this

Don't use this when

Mutating the model — pure grouping.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Resolve input ids: element ids (Bot) else active selection (Human).
2) WireError if fewer than 2 element ids (nothing to thread).
3) angle_tol_deg = angle tol deg ?? 5.0; lateral_tol_mm = lateral tol mm ?? 300.0.
4) Call CombineBoundingBoxesSafely.Combine(doc, ids, angle, lateral).
5) Serialise threads + unthreaded into tracker outputs.
6) Human path: TaskDialog summary "N threads, X unthreaded".

What you'll see in the chat

on start
Combining parallel services into threads…
thinking
Resolving input element ids…
Calling CombineBoundingBoxesSafely…
on success
{threads_count} threads; {unthreaded_count} unthreaded.
on failure
Thread detection 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_detect_thread_of_services_and_combine_bounding_boxes
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolverdetectthreadofservicesandcombineboundingboxes · thread of services · combine parallel bb

PillarClash Manager / Solver