Commands  ›  Clash Manager / Finder  ›  Clash Finder Run By Workset Pairs

Clash Finder Run By Workset Pairs

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

Coming soon

Before you run this

Workshared model; worksets available; at least one element per workset.

After it runs

Clashes upserted per workset pair.

When to use this

Don't use this when

Non-workshared models — WireError.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) If doc is not workshared → WireError.
2) workset pairs default to [(MEP|Mechanical|Electrical|Plumbing, Structural|Structure)].
3) For each pair: resolve WorksetId by name match; collect elements per side via ElementWorksetFilter.
4) Delegate pipeline.Run.
5) Aggregate + emit summary.

What you'll see in the chat

on start
Running clash detection by workset pairs…
thinking
Resolving workset ids by name…
Delegating pipeline.Run per pair…
on success
Workset-pair detection wrote {total} clashes.
on failure
Workset-pair 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_by_workset_pairs
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashfinderrunbyworksetpairs · clash by workset pairs · discipline boundary clashes

PillarClash Manager / Finder