InterferenceCheck.Parse

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.

Revit_2016-01-31_20-45-03.png

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:

Revit_2016-01-31_20-45-32.png

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

Revit_2016-01-31_20-46-55.png

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.

Advertisements

ErrorReport.Parse

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

Revit_2016-01-31_19-15-37.png

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:

Revit_2016-01-31_19-16-12.png

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

Revit_2016-01-31_20-05-28

Dictionary.ByKeysValues

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).

DynamoSandbox_2016-01-31_18-43-25.png

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.

The dictionary values can hold lists of objects:

DynamoSandbox_2016-01-31_18-58-39.png

Or Revit elements:

Revit_2016-01-31_18-59-53.png

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

DynaWorks Node Index

DynaWorks is maintained by Adam Sheather, see this post on DynaWorks 16.

On github at https://github.com/Gytaco/DynaWorks

AppendFile
ClearClashResults
GetCameraPoint
GetClashBoundingBox
GetClashDetection
GetClashGroupResults
GetClashNodes
GetClashPoint
GetClashResultComments
GetClashTests
GetDirectionPoint
GetFilesInProject
GetNavisAttributesFromNodesList
GetNavisAttByClassName
GetNavisAttByClassUserName
GetNodeChildren
GetNodesFromSelectionsSets
GetObjectNames
GetObjectValues
GetPropertiesList
GetSavedViewCommentsByName
GetSavedViews
GetSelectionSetsInProject
GetSuitableDirectionPoint
GetSuitableEyePoint
GetValuesAsStringClassName
GetValuesAsStringClassUserName
GetView
GetViewDirection
mGetCamerPoint
mGetClashBoundingBox
mGetClashPoint
mGetDirectionPoint
mGetSuitableDirectionPoint
mGetSuitableEyePoint
mGetViewDirection
NodeByClassNameList
NodeByClassUserNameList
OpenFile
PublishFile
RemoveResolved Clashes
RunAllTests
SaveAs
SaveFile
StayOpenFile

BumbleBee Node Index

Maintained by Konrad Sobon. Instructions and tutorials can be found at www.archi-lab.net. This is an open source project with GitHub page: https://github.com/ksobon/Bumblebee as well as an open source primer: https://github.com/ksobon/BumblebeePrimer. You can read the primer here: http://konradsobon.gitbooks.io/bumblebee-primer/content/

(2) Color Scale Format Condition
(3) Color Scale Format Condition
BB Data
BB Style
Border Style
Cell Index
Cell Value Format Condition
Chart Style
Clear Contents
Conditionally Format Excel
Data Bar Format Condition
Expression Format Condition
Fill Style
Format Excel
Get Worksheet Names
Graphic Style
Label Style
Legend Style
Line Chart Graph Style
Line Chart
Line Style
Live Write Excel
Marker Style
New File By Template
Pie Chart Graph Style
Pie Chart
Read Excel
ReadExcel.ByRange
Search Value Get Row
Text Style
Top/Bottom Percentile Format Condition
Write Excel

bumblebee

Ampersand Node Index

Package maintained by Colin McCrone

Circle.ByPackingAlongCurve
ColumnGrid.Line
List.ChopByLengths
List.GroupByContainer
List.GroupByKey
List.QuadsFromGrid
List.SelectSetByKey
List.SortAzimuthally
List.SortByKey
List.StringSequence
List.TakeByKey
Math.Sum
Object.GetTypeAsString
Pentagram
Point.SortAzimuthally
PolyCurve.ByCurves
PolyCurve.IsClockwise
Surface.TrimAll
Vector.ByAltitudeAzimuth
Vector.ProjectToPlane
View.SetPerspectiveCamera