Commands  ›  Clash Manager / Finder  ›  Clash Finder Run On Visible Elements In Current View

Clash Finder Run On Visible Elements In Current View

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

Coming soon

Before you run this

Active document + active view; at least one MEP category populated in the view.

After it runs

Clashes upserted into the staging DB per category pair in-view.

When to use this

Don't use this when

Full-model detection — use the main Run command.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) view = view id-resolved OR active view.
2) Iterate canonical category pairs (same set as main Run command).
3) Set A = FilteredElementCollector(doc, view.Id).OfCategory(catA).WhereElementIsNotElementType().
4) Set B = FilteredElementCollector(doc, view.Id).OfCategory(catB).WhereElementIsNotElementType().
5) Delegate pipeline.Run(doc, rule, setA, setB).
6) Aggregate + emit per_pair summary + totals.

What you'll see in the chat

on start
Running clash detection on current view only…
thinking
Collecting visible elements per category pair…
Delegating to FindClashesBetweenTwoElementSets…
on success
View-scoped detection wrote/updated {total} clashes.
on failure
View-scoped 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_visible_elements_in_current_view
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashfinderrunonvisibleelementsincurrentview · run clashes visible only · view scoped clash finder

PillarClash Manager / Finder