IFC Clash Detection icon

IFC Clash Detection

Detect spatial clashes between IFC models, for documentation see Ifcopenshell.

Detect Clashes

AI-generated

Overview

This node performs IFC (Industry Foundation Classes) clash detection between spatial models. It is useful in construction and architectural workflows to identify conflicts or collisions between different building elements represented in IFC files. For example, it can detect if a pipe clashes with a wall or if structural elements intersect improperly. The node supports filtering elements within IFC files, setting detection modes (intersection, collision, clearance), and grouping options to customize the clash detection process.

Use Case Examples

  1. Detect clashes between two sets of IFC files representing different building systems.
  2. Filter elements by type (e.g., walls, beams) to focus clash detection on specific components.
  3. Use smart grouping and tolerance settings to refine clash detection results and reduce noise.

Properties

Name Meaning
Clash Set Name The name of the clash set to identify the group of clashes.
Output Filename The name of the output file where the clash report will be saved.
Group A Files A collection of IFC files for group A, each with optional element selectors and inclusion/exclusion modes to filter elements for clash detection.
Group B Files A collection of IFC files for group B, each with optional element selectors and inclusion/exclusion modes to filter elements for clash detection.
Options Various options to customize clash detection behavior, including allowing touching elements, checking all elements, clearance value, max cluster distance for smart grouping, detection mode, smart grouping toggle, and tolerance value.
Wait for Completion Whether to wait for the clash detection job to complete before continuing the workflow.
Polling Interval (Seconds) How often to check the job status if waiting for completion.
Timeout (Seconds) Maximum time to wait for job completion before timing out.

Output

JSON

  • job_id - The identifier of the submitted clash detection job.
  • status - The status of the clash detection job.
  • result - The clash detection results, including detected clashes and metadata.

Dependencies

  • An API key credential for the IFC Pipeline API to submit clash detection jobs and poll for their completion.

Troubleshooting

  • Ensure the IFC files specified exist and are accessible; invalid file references will cause errors.
  • Selectors must follow IfcOpenShell syntax; incorrect selectors may result in no elements being selected or errors.
  • If waiting for job completion, network issues or long processing times may cause timeouts; adjust polling interval and timeout settings accordingly.
  • API authentication errors may occur if the IFC Pipeline API credentials are missing or invalid.

Links

Discussion