15 March 2019


I have seen it over and over again. Users calling Dynamo "graphs" as "scripts". Sorry but this is not what it is!

What we do with Dynamo is much smarter, it is directed graph technology. It is a much higher order way to do (visual) programming, than simple scripts known from ex. Java scripts, or even the way Python scripts is widely used in Custom Nodes... or scripts in Code Blocks.

Naming it "scripts" is to patronize what we actually do.


Try also to open a dynamo 1.3 file in a text editor...
  <Dynamo.Graph.Connectors.ConnectorModel ... />

Or take a look at the Dynamo Primer...

...and from https://primer.dynamobim.org/13_Best-Practice/13-2_Graph-Strategies.html

Reduce Complexity
As you develop your Dynamo graph and test ideas, it can quickly grow in size and complexity. While it is important that you create a functioning program, it is equally important to do it as simply as possible. Not only will your graph run faster and more predictably, you along with other users will understand its logic later on. The following are several ways that will help you clarify the logic of your graph.


Maintain Readability

In addition to making your graph as simple and efficient as possible, strive for graphic clarity. Despite your best efforts to make your graph intuitive with logical groupings, relationships might not be readily apparent. A simple Note inside of a Group or renaming a slider can save you or another user from unnecessary confusion or panning across the graph. The following are several ways that will help you apply graphic consistency within and across your graphs.

It does matter to use a "language" thoroughly. Giving up language is giving up the core of whatever a culture stands for. Therefore, I don’t think it is a good idea to let "slang" become the language!

Please let us use the right notation... it is graphs, not scripts!

10 March 2019

50 new nodes for materials

The update x.4.1 includes a new branch for “Materials” and +50 new nodes handling generic material assets, appearance-, physical-, and thermal assets.

Material general


Physical and Thermal


25 February 2019

IFC export and some other new nodes

The major update release (134.4.0 and 202.4.0) includes nodes for IFX export.
The nodes is build using the API from the IFC exporter 18.4.0 (for dynamo 1.3.x) and 19.1.0 (for dynamo 2.0.x), meaning the exporter must be installed to use these nodes!

Building the exporter nodes made me realize that some project nodes also was needed

Dropdown for families in the project and selection of all elements by family in the document added.

String.Substring and String.Replace added, these takes lists as input!
can be used for "manually" migration of dynamo files

09 February 2019

Open new view ... active view

I have made a node for opening a new view, this new view will then be the active view when the graph is finished and the dynamo application again is idle. However, this is only one half of what I would like to be able to do with my node. My goal was to be able to close the other open windows in the same process.

That is not possible at the moment due to the way Dynamo works. If it should be possible I need the ability to use events inside a method in Dynamo like this post by Jeremy Tammik describes.

Therefore, is the workaround at the moment as following. Add the “OpenView” node in a graph and then execute the graph and do whatever is needed. When you eventually has finished doing whatever you should, then save and closes the file.

When the file is re-open will the last view be the default view unless starting view is set, in that case, will it be the starting view and that would be correct in those cases.

This new node cannot be called as a background action!

04 February 2019

Associate and Category

Orchid version 134.3.11 / 202.3.11 has been released.
The latest update includes a larger extension of nodes for association.

New node for nested associated elements in families (orange box in image) and node for parameters to verify if "HasAssociated" elements.

Association for global parameters. Associate, GetAssociate and HasAssociated.

Verify if "Family" and FamilyType" has associated elements

Several nodes for Category. Get all built in categories, categories in document, categories by category type and lastly get the category type from categories.

New node for SetType. The node takes an "element" and a "familyType". the element gets the "FamilyType". This can be used when elements need a new type ex. when randomizing. Besides is two new nodes for random created. These nodes take a "range" and return random number(s) in the range. The OOTB node gives the random number in the range 0 to 1.

03 February 2019

Migrate Custom Nodes to Zero Touch nodes

Yet another time has a user problems in migrating a graph using Custom Nodes which are deprecated to the comparative Zero Touch node. It seems there still exist users who cling to to my long-gone DanEDU package which was a CN based package because it is a job to migrate it using my new ZT based package (Orchid)

I have tried if there was any possibility to add old CN nodes in my migration, but that is not possible.

However, I did try to solve this issue for the user, and figured that it is doable to do a “manually” migration using a notepad editor, and it was not that difficult...

It is a good idea to make a dummy file with the corresponding nodes you want to use because you need to know where the assemblies are stored and what the names are, the easiest is to create a graph with the nodes you know you need and then open this file in a notepad so you have the strings you need to replace values with!

The below example is from a 1.3.x graph, since the old graph most likely is from the era with the old layout before the 2.0.x versions.

The below is the node "List.Clean|DanEDU"
<Dynamo.Graph.Nodes.CustomNodes.Function guid="e4e4649b-af37-41d3-bde8-29c4e9181d4a" type="Dynamo.Graph.Nodes.CustomNodes.Function" nickname="List.Clean|DanEDU" x="281.221049098559" y="999.174659610855" isVisible="true" isUpstreamVisible="true" lacing="Shortest" isSelectedInput="False" IsFrozen="false" isPinned="false">
  <PortInfo index="0" default="False" />
  <PortInfo index="1" default="True" />
  <ID value="f39ad724-9216-46d6-9cfc-0e9bb8a71360" />
  <Name value="List.Clean|DanEDU" />
  <Description value="Remove empty list, null and blank values
- former named as RemoveNull" />
    <Input value="list" />
    <Input value="searchFor" />
    <Output value="list" />

The below is the ZT node “List.Clean” in the Orchid package
<Dynamo.Graph.Nodes.ZeroTouch.DSFunction guid="f166a310-a158-4778-b709-8eb190e878c8" type="Dynamo.Graph.Nodes.ZeroTouch.DSFunction" nickname="List.Clean" x="-0.0783702393594012" y="999.174659610855" isVisible="true" isUpstreamVisible="true" lacing="Shortest" isSelectedInput="False" IsFrozen="false" isPinned="false" assembly="..\..\AppData\Roaming\Dynamo\Dynamo Revit\1.3\packages\Orchid\bin\OrchidGeneric.dll" function="Orchid.Generic.Core.List.Clean@var[]..[],var[]..[]">
  <PortInfo index="0" default="False" />
  <PortInfo index="1" default="True" />
The most important part to keep is the guid mention in the first line after the function, ex. guid="e4e4649b-af37-41d3-bde8-29c4e9181d4a". The guid is the id used in the graph as the connector!
example where a “codeblock” with the connector guid="f7fc68c8-1239-46d9-848c-ef958450c6de" connects to the “List.Clean|DanEDU” node
<Dynamo.Graph.Connectors.ConnectorModel start="f7fc68c8-1239-46d9-848c-ef958450c6de" start_index="0" end="e4e4649b-af37-41d3-bde8-29c4e9181d4a" end_index="0" portType="0" />

Therefore be exceptional observant towards these guid’s!
Likewise do not change the x, y position for the node ex.
x="281.221049098559" y="999.174659610855"

REPLACE to “List.Clean” node
The first string to replace is Dynamo.Graph.Nodes.CustomNodes.Function with Dynamo.Graph.Nodes.ZeroTouch.DSFunction
-– this will replace all the CN nodes functions!!! -–
Next string to replace is nickname="List.Clean|DanEDU" with nickname="List.Clean"
Then add the assembly in the end of the line with isPinned="false">
extend this to isPinned="false" assembly="..\..\AppData\Roaming\Dynamo\Dynamo Revit\1.3\packages\Orchid\bin\OrchidGeneric.dll" function="Orchid.Generic.Core.List.Clean@var[]..[],var[]..[]">
Move on to the other nodes, replacing only the last two strings per node!
Thats it... all the other strings from the “old” node will be removed when you open the graph, then you are good to go...

Try this out by your self...

danedu nodes.dyn
danedu nodes-migrated.dyn

This post is originally published at dynamobim.org

21 January 2019

HasAssociated and Convert

New release there includes some new nodes...

Check if family parameter has associated element (...in upper right corner).
PostEdit: Associate nodes is updated

Node there converts shared parameters to family parameters.

After the last update of all family document nodes, is all nodes also updated changing the output to the most suited instead of document as output.

This post is originally published at dynamobim.org