DESCRIPTION
Generates a report of all CAD links and imports in the active Revit document. The node provides detailed information on: instance name, link status, view specific, owner view id, workset name, file path and host level. Linked and Imported CAD links are output into lists to aid with CAD file management in Revit.
To report the active Revit document, leave the filePath input unconnected. To report any external Revit file or Family silently (without opening) simply input its file path using an out-of-the-box File Path node.
MORE INFO
Visit Bimorph Nodes for more information and downloadable example graphs
INPUTS
sheets : Sheet[]
run : bool
duplicateWithViews : bool
duplicateOption : int
suffix : string
prefix : string
OUTPUTS
report[] : string[]
Sheet[] : Sheet[]
DESCRIPTION
Duplicate selected Sheets with options to specify the duplication of placed Views and the method of duplication. The node will identify illegal characters in View names (such as {3D} for example) and clean them automatically to circumvent unexpected failures.
The algorithm which controls the duplicate View behaviour has been designed so that dependent Views are duplicated from a newly created parent View to maintain the existing View structure. The node will also check if the parent View exists on subsequent runs to handle situations where any of its other dependent Views need to be duplicated.
The report output provides a detailed log of any Sheets that fail to duplicate, any Views that fail to duplicate or cant be placed, and View names cleaned of illegal characters.
MORE INFO
Visit Bimorph Nodes for more information and downloadable example graphs
I have just added two nodes to the Data-Shapes package:
GetLinkedElements.ByHostView
GetLinkedElements.ByHostViewAndCategory
The names of the nodes are pretty explicit: they gather elements in linked documents visible in a host view.
GetLinkedElements.ByHostView uses the visibility settings of the host view when collecting the linked elements, whereas GetLinkedElements.ByHostViewAndCategory allows you to set the categories you’re interested in collecting.
Both nodes can be found in Data-Shapes Package (version 2017.02.20).
I recently sliced off a few nodes focused on package management and have placed them in a new package called RollingPin.
Current Node List:
Check DYF folder for Dependencies in Package Folders
Get DYF Dependencies for One DYF File
Get DYF Dependencies through Recursion v1
List Nested Node Nicknames for Folder
List Nodes in DYFs for an Entire Folder
Node Names From Directory String
Package Folder Details
Report Dynamo Package Details by Folder
Show Dependency Ids for one DYF
Show Dependency Nodes for one DYF
Summary and Node Search for a Folder of DYFs
With Revit 2017 Update 1, the Dynamo Player is now available to run DYN files from a monitored folder directly, without opening the Dynamo application.
The workflow assumed that the model contains all trades in one file. But most of cases each trade exists in its own file and based on the linking technique used in your firm the relation between the trades projects defers.
In this example I assumed that the architecture linked the piping file to the base model project, because most of cases the architect will be the responsible for making the opening in the walls of his model.
Nothing changed from the Create Floor Opening for Vertical Pipes in Revit 2016 using Dynamo tutorial except the technique of getting the pipe elements. In the previous tutorials we addressing the pipe elements directly from the current model, but now we will access them through the Link file.
The “Get all Pipes from link” Node is pure Python Script that get the link documents from the current project then collect the Pipes Category and set them as its output. The workflow then continues as it is in the Create Floor Opening for Vertical Pipes in Revit 2016 using Dynamo tutorial.
This node will take a flat Surface, and create a ‘Slatted Facade’ from said surface.
You can customise the Facade Thickness, Tool Amount, Slat Amount and Slat Thickness.
Note: This node includes randomisation variables, so every time you change some of the input values the entire geometry will change. It will also currently only work on vertical flat surfaces.
This node will take a series of close model lines and output a points list based on a chosen resolution (Default resolution is 20). It will output the information in both a Single Point list and a Grouped Point list based on the X-Coordinates of each point.