Commands  ›  Clash Manager / Finder  ›  Clash Finder Run On Selection Against Rest Of Model

Clash Finder Run On Selection Against Rest Of Model

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

Coming soon

Before you run this

Active document; selection (resolver or active) of ≥ 1 element.

After it runs

Clashes upserted for pairs (selection × rest).

When to use this

Don't use this when

Full model or view-scoped — use the other Run commands.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) ids = element ids OR current selection (active view). WireError if empty.
2) set_a = resolve ids → Elements; drop nulls.
3) set_b = all MEPCurves + MechanicalEquipment in doc minus set_a ids.
4) pipeline.Run(doc, "selection_vs_rest", set_a, set_b).
5) Emit per_pair + total_upserted.

What you'll see in the chat

on start
Running clashes for selection vs. rest of model…
thinking
Resolving selection and candidate pool…
Delegating pipeline.Run…
on success
Selection-vs-rest produced {total} clashes.
on failure
Selection-vs-rest run 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_finder_run_on_selection_against_rest_of_model
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashfinderrunonselectionagainstrestofmodel · selection vs rest · targeted clash probe

PillarClash Manager / Finder