Month: January 2016

dimven

FamilyInstance.ByGeometry

This node converts a Dynamo surface, poly-surface or solid into a Revit family. It then places an instance of that family inside your project, reflecting the geometry position from inside Dynamo. It currently supports Revit 2014 to 2016.

Revit_2016-01-12_21-53-47.png

The most important inputs are:

  • The geometry objects
  • A file path to a family template (It is crucial that the family template version matches your Revit version)
  • A unique family name for each geometry object

The optional inputs are:

  • Category. The default value is Generic Model. Some templates, like the conceptual mass, do not allow changes to the family category. In those cases the built-in category will remain in force.
  • Material of the family, provided as a string. The material must be pre-loaded into the template for this option  to take effect. If a material with such a name does not exist in the template, the default “By Category” material will be used.
  • Void switch provided as a Boolean ( true / false). The default value is set to false. If you provide a true value, the newly created family will act a void cut element and will be able to perform cuts on  structural elements, generic model elements and host elements.
  • Subcategory provided as a string. The default value is null – meaning that this option is ignored. If you provide a subcategory name, it will be generated inside the family document, applied to the family and added to the project together with it.

 

Revit_2016-01-12_22-21-28.png

Do note that by default, the node works in “longest” lacing. That means that if any of the optional inputs are less than the geometry objects and the family names, the last input will be used for all remaining families. In the above image, the families at [6] and [7] will belong to the “Generic Model” category and will act as void cuts.

You can download this sample and others from the Spring Nodes repository:

https://github.com/dimven/SpringNodes/tree/master/Samples

Currently the node does not place multiple geometries into a single family. There is a partial workaround described in the following discussion:

https://github.com/dimven/SpringNodes/issues/10

A node for such cases might be developed in the future.

lukesjohnson

All Elements of Category

This is one of the simplest ways to select Revit objects in Dynamo. Simply feed a Categories selection into this All Elements of Category node, and after the script is Run, those objects will be selected in the Dynamo session.

revit-categories

lukesjohnson

Types of Posts on Dynamo Nodes

There are a few different types of posts on Dynamo Nodes, but they should all follow the basic rules on this page.

We recommend that you choose from one of these 7 different types of posts…

1) Basic Node Post
This post will have this basic Template:

  • Post title as Node Name (for duplicate names, use (Variant: ) after node name)
  • A brief Description if possible
  • A single, Reference image or screenshot of a Dynamo graph showing that node in Use
  • Source URL or attribution
  • Any relevant Download links, preferably using the Dropbox folder

2) Detailed Node Post
This template contains more information, such as:

  • Post title as Node Name (for duplicate names, use (Variant: ) after node name)
  • Description containing: practical, real world use case for this node, and what the node actually does to assist in solving that problem
  • 1 x Reference Image
  • Inputs: details on the input data type/screenshots
  • Outputs: what comes out of this node after it is Run?
  • Download links: especially to DYN examples, but also including to RVT, csv, xls or RFA samples if these apply
  • Additional Images: including more real world graph screenshots, and also images showing the internal working of the node (DYF)
  • Uses: what other workflows can this node facilitate?
  • Source URL or attribution
  • Links to related posts on DynamoWorks
  • Future Development: if you are the node developer, what plans do you have to develop this node further?

As you can see, a Basic Post can be edited and converted to a Detailed Post, simply by adding the extra information.

3) Workflow Post
This is a way to share completed script workflows, typically as a DYN script attached to the post. These should be added to the Category Workflows in WordPress, and the post title should begin with Workflow:

4) Package Overview Post
If you would like to share an overall aim or story related to a specific package, please do this once for each package only, Tag with PackageDescription, and title the post like this:
What is PackageName?

5) Package Index
This post type is a list of all nodes in a specific package. Initially, this should be a flat list of Node names in text format, and then links can be added as each node page is posted to Dynamo Nodes. Tag with PackageIndex. We can use various tools to update these pages from time to time.

6) Resource Post
This post type is a way to share or re-share useful Dynamo resources that appear on other sites. Categorize as Resource Links. Tag with ResourceSharing. Begin post name with Resource:

7) Video Post
This is a way to share or re-share training or demonstration videos, related to Dynamo or DynamoBIM generally. Categorize as Videos. Tag with VideoSharing. Begin post title with Video:

josteinberger

QRcode

Creates QR codes based on a string input. Accepts single arguments as well as lists. There is also support for color and adjustment to the error correction level. (See QR.ECClevel)

Inputs:

  • Str: single string or list of strings to be encoded.
  • QRColor: Dynamo color
  • BackColor: Dynamo color
  • ECCLevel: string (“L – 7%”, “M – 15%”, “Q – 25%” or “H – 30%”)

QrCode workflow

 

Source: http://jbdynamo.blogspot.no/2016/01/qr-codes-in-dynamo-revisited.html