Process a Revit interference check report (HTML file) and extract the clash types (the categories of the clashing elements), all clashing elements and the total number of clashes. To generate an interference report in Revit, go to Collaborate > Interference Check > Run Interference Check.

Inputs:

• report: a file path to the location of the report.
• fetch_elements: a Boolean toggle (True by default). When true, the node will attempt to fetch the elements involved in each clash. For this to be successful, the node must be executed from the Revit document that the report originated from. If the element does not exist any more, a null value will be returned instead. If you are executing from a different document (or from Sandbox mode), be sure to set “fetch_elements” to False. This will give you the ID of each element as a string for easy documentation.

Outputs:

• clash categories: all clashes in the report.
• affected elements: the elements involved in each individual clash.
• unique cases: each type of clash is listed here only once. Use this to filter in a specific type of clash (and thus its elements).
• number of clashes: a count for each unique clash type and the sum of all clashes found in the report. Useful for documentation purposes.

The expected result when “fetch_elements” is set to False:

An example on how to filter a specific type of clash and fetch only its elements:

In very limited cases, a clash type may not be recognized successfully and will be categorized as “Unidentified”. Please report those cases to the repository.

Process a Revit error report (HTML file) and extract the error types, all affected elements and the total number of errors.

Inputs:

• report: a file path to the location of the report
• fetch_elements: a Boolean toggle (True by default). When true, the node will attempt to fetch the elements involved in each error. For this to be successful, the node must be executed from the Revit document that the report originated from. If the element does not exist any more, a null value will be returned instead. If you are executing from a different document (or from Sandbox mode), be sure to set “fetch_elements” to False. This will give you the ID of each element as a string for easy documentation.

Outputs:

• error messages: all error messages in the report.
• affected elements: the elements involved in each individual error.
• unique errors: each type of error is listed here only once. Use this to filter in a specific type of error (and thus its elements).
• number of errors: a count for each unique error type and the sum of all errors found in the report. Useful for documentation purposes.

The expected result when “fetch_elements” is set to False:

An example on how to filter a specific type of error and fetch only its elements:

Dictionaries are an incredibly powerful tool for making associative sets between two equal length lists. The first is a list of keys (or indexes) and the second – a set of values (or the data that will be returned for each index).

Inputs:

• keys: it must consist of unique strings or numbers.
• values: a value that will be returned for each key.
• search keys: the list of keys(indexes) that you want returned.

—
Manipulate data, sculpt geometry, explore design options, automate processes by remotely accessing your visual programming environment on trending virtual PCs from CloudDesktopOnline.com powered by one of the best DaaS providers – www.Apps4Rent.com.
—

The dictionary values can hold lists of objects:

Or Revit elements:

If a search key is not found in the dictionary, an empty list will be returned instead.