andydandy74 / clockworkfordynamo

A collection of 450+ custom nodes for the Dynamo visual programming environment

Clockwork is a collection of custom nodes for the Dynamo visual programming environment. It contains many Revit-related nodes, but also lots of nodes for various other purposes such as list management, mathematical operations, string operations, geometric operations (mainly bounding boxes, meshes, planes, points, surfaces, UVs and vectors) and paneling. Currently it consists of some 450+ nodes of which a large portion was originally published in a number of separate packages.

Clockwork for Dynamo 2.x is currently developed in Dynamo 2.6.0 but also tested in newer 2.x versions which means it's compatible with Revit 2021 and later (and probably still working in Revit 2017-2020 as well).

Installation

Installation is simple - just use Dynamo's built-in package manager and search for Clockwork. Make sure you have the correct version of Clockwork installed that corresponds to your installed version of Dynamo (most likely 2.x). As of Revit 2023 you will need to install the package "DynamoIronPython2.7" (also from the package manager). Dynamo's workspace reference view extension will prompt you to install version 2.1 of that package. Don't do that! Instead install the latest version of that package.

Versions

The different versions are available as separate packages on the package manager. (So far each new major Dynamo version has introduced changes that prevented downward - and sometimes even upward - compatibility of nodes, hence the separate packages...)

Package name	Supported	Last version	Revit versions	Change log	Docs	Repository	Deprecated nodes	Samples
Clockwork for Dynamo 2.x	✅	2.6.0	2017-24	Changes	Docs	Repo	Deprecation	Samples
Clockwork for Dynamo 1.x	❌	1.34.0	2015-19	Changes	Docs	Repo	Deprecation	Samples
Clockwork for Dynamo 0.9.x	❌	0.90.8	2015-17	Changes	Docs	Repo	Deprecation
Clockwork for Dynamo 0.8.2	❌	0.82.8	2014-16	Changes	Docs	Repo	Deprecation
Clockwork for Dynamo 0.7.x	❌	0.75.47	2014-16	Changes	Docs	Repo	Deprecation	Samples
Clockwork for Dynamo 0.6.3	❌	0.63.3	2013-14		Docs	Repo	Deprecation	Samples

Note that Clockwork version numbering follows the Dynamo version the package is currently maintained for, e.g. Clockwork for Dynamo 2.x v2.0.XXX is maintained in Dynamo 2.0.0 while Clockwork for Dynamo 2.x v2.3.XXX would be maintained in Dynamo 2.0.3 and Clockwork for Dynamo 2.x v2.30.XXX would be maintained in Dynamo 2.3.0...

Renamed, recategorized and deprecated nodes

During migration from one Dynamo version to the next, I regularly recategorize, relabel and rename a lot of nodes. These changes are documented in an excel sheet that contains a list of all nodes within the package.

Material on this repository

This repository contains the following:

• Directory maintenance contains scripts that I use to keep Clockwork in shape, e.g. for creating the node documentation on the wiki, extracting Python scripts from custom nodes etc.
• Directory nodes is the actual repository of the custom nodes that I use for versioning nodes in between publishing package updates to Dynamo's package manager - which means you will sometimes find nodes in here that haven't made it onto the package manager yet.
• Directory package_samples contains simple examples for most of the nodes in Clockwork. I use them for occasional testing, but they should also help explain how to use each node. All samples are available for the current versions - sample support for older versions is patchy at best.
• Directory workflow_samples contains some old sample workflows that I have published online somewhere before. I have also included some of the examples that I used to use for teaching Dynamo as well as some material presented at conferences. Almost all of these are available for Dynamo 0.7.x (as well as 0.6.3). They will not be updated to a current version.

Sponsoring?

This is free software. I've created and maintained it on my spare time for a number of years now. I don't do Patreon or GitHub Sponsors and I'm not planning to. However, if you are using this software or have done so in the past and it has increased your productivity, please consider giving something back nonetheless. If you're smart enough to use Dynamo, you're most probably smart enough to know climate change is real, too. And I'd like to believe you're already doing something to battle it at this point.

Do more.

clockworkfordynamo's Issues

Add info on limitations to Clipboard nodes

"only on top of Revit" etc.

Filter.ByInstParamValue

In the CN, I've edited my local dyf to use A equal B instead of ==, it allows me to use object comparison (like phases). not tested any further with strings though....

Add SpatialElementBoundaryLocation options to Room.Boundaries

Make four nodes for these options and alter Room.Boundaries accordingly

Allow single element arguments for famtype in FamilyInstance.SetType

Use case:
http://dynamobim.com/forums/topic/problems-with-familyinstance-settype-from-clockwork-package/#post-9366

Vector.AltitudeAndAzimuth returns null in some cases

Test this with SunDirectionToPanels workflow

0.8 migration - Deprecation

Check to see which nodes can be retired.
All deprecated nodes are to be listed here: https://github.com/CAAD-RWTH/ClockworkForDynamo/wiki/Deprecated-Nodes#candidates-for-deprecation-in-clockwork-for-dynamo-08x

Unmigrated nodes

Check if these make sense at all in 0.7:

• Combine List With Nested List
• Move XYZs From Plane To Plane

Booleans for Create/Modify nodes

All create/modify nodes should have a boolean output that indicates if the operation was successful

Topography.IntersectionWithPlane

I can't seem to get this node to work in daily 0.8.2? I get only null values.

Update Wall.ByFace node description

http://dynamobim.com/forums/topic/create-wall-by-face/#post-13306

PythonExtracter: Search/Replace some HTML chars

Greater than (>) and lower than (<) need to be replaced...

Rework Vector.AltitudeAndAzimuth

Lose the Formula nodes as soon as this one's resolved:
DynamoDS/Dynamo#3106

Multi-category filters for filtered element collectors

Several of the nodes using a filtered element collector might gain better performance from using a multi-category filter. Need to check whether this affects any workflows that expect lists of elements grouped by category. If feasible, implement for these nodes:

• All Families Of Category
• All Family Types Of Category
• All View-Dependent Family Instances Of Category

Migrate remaining samples to 0.7

• ComponentLayoutForCNC
• HarvestDome

Update custom surface division sample

Add some alternatives:

• by formula
• by ratio
• by alternating rows
• individually by row

List.ChopByLengths not taking lengths list with just one item.

The List.ChopByLengths node doesn't seem to like it when I put in a number instead of a list of numbers (part 1). Also it doesn't flatten the list when the length of the input list is equal to the given number (part 2).
Now you might wonder why I use this node then. That's because sometimes the the lengths input is, and sometimes it isn't, just one single number. Of course it does work when I put in several numbers, I would just like it to work with a single number out of the box, too. :)

Place Unplaced Room

need that node!

Rework the TextNote node

see changes & comments by @ksobon here:
http://dynamobim.com/forums/topic/textnote-bystringandposition-is-it-possible-to-expand-the-resulting-textnote/#post-12315

Rework Room.DoorsOrWindows

• Reconsider dividing this into two separate nodes or use a boolean switch instead of a category input
• For processing multiple rooms this currently has to be used in conjunction with a List.Map node - not so comfy

All Intersecting Elements Of Category does not find intersections

The ReferenceIntersector works fine in 0.6.3, but doesn't find intersecting elements in 0.7

Run node to code on all custom nodes

Most of the nodes are already code block based but let's make sure that all nodes have been optimized as much as possible.

0.8 migration - Default values and data types for inputs

Check all nodes for inputs that qualify:
DynamoDS/Dynamo#3233

Samples: Check notes for project files

Check all samples if they contain a note that says which Revit model to run it on

Rework DoorOrWindow.ExitsToOneRoomOnly

Get rid of the IsNull nodes once this one's fixed:
DynamoDS/Dynamo#2506

Issues in relation to 3D views & view templates

So there's a strange bug in Dynamo that prohibits accessing 3D view templates:
DynamoDS/Dynamo#2970
(Which also means View.ViewTemplate returns null for all views that have a 3D view template assigned to them...)
As soon as this is resolved, deprecate Document.Views ...

View.Plane node

The View.Plane node doesn't regenerate when I hit run after I've moved a section in the Revit document. Is this intentional?

Restore dictionaries in PathGraph nodes

Migrate these nodes as soon as this one's fixed:
DynamoDS/Dynamo#3100
(or rewrite it altogether)

0.8 migration - Icons

Add an icon resource file as soon as this functionality becomes available for custom nodes...

Point.Average not working CBN-based

Just returns null.
Need to re-check this in future Dynamo versions - also check UV.Average...

Customized List.AllTrue/AllFalse

I need this to be stricter than the built-in nodes. Empty lists should return false.
See this discussion:
DynamoDS/Dynamo#4940

Element.ParameterExists in 0.8.1

This node seems not working in Dynamo 0.8.1, I will go back to 0.8.0 since it's use in my daily work, just let you know the issue.
Thanks for your great works!

Rework List.AnyFalse/AnyTrue

As suggested by @dimven on Facebook the other day, these nodes could be simplified by using a syntax like Not(AllFalse(mylist)).

suggestion: Rename "DetailCurve.FromCurve"

Renaming the node to "DetailLine.FromCurve" could possibly make it easier to find for new users.

Paneling.TriangularFlatMirrored not working properly

Except for the first output, all other outputs return null...

Only keep Element.Panels temporarily

Element.Panels can be deprecated as soon as this one has been resolved:
https://github.com/DynamoDS/Dynamo/issues/4128

All Instances of Family Type

would be useful...

Check Document.ProjectPosition against built-in functionality

Looks like there are built-in nodes for querying latitude and longitude now. Check if that pertains to any of the other outputs of Document.ProjectPosition as well.

Source Code

Andy, If possible did you think about posting the source code for all nodes as well? I am talking especially about nodes that have custom Python nodes. It's just easier to contribute when one can see the code clearly instead of in context of a *.dyf file formatting.

Migrate custom nodes to CBNs

Some of the custom nodes are still completely node-based. They should be converted to CBNs.

Vertical Intersects dependent on start / end point order

This affects both DividedSurface.VerticalIntersectsByEndpoints and DividedSurface.VerticalIntersectsByEndpointsAndFunction. In some cases, depending on the order of start and end point, some of the refplanes cannot be created.

Cut panels for hexagon paneling

Paneling.Hexagonal currently only returns hexagonal panels. Any cut panels at the surface edges are being ignored. These should be computed as well and be returned through separate ouput ports (left / right / top / bottom) and receive options for reversing and shifting.

0.8 migration - Test Lacing for Python Nodes

The new lacing ability for custom nodes may also be interesting for Python-based nodes, i.e. it may mean that it is no longer necessary to build loops into those nodes and wrap them with Turn Into List and ReturnListOrSingleValue nodes.

Run a performance test with a large number of elements to see if it is feasable to convert those nodes so they work on single item arguments. My hunch is that it's either not as simple as I think or that the performance would actually suffer (due to calling the same Python node over and over again). But test it we shall.

0.8 migration - Units

Check all nodes for inputs and outputs that use units.
Make a list of affected nodes.
Wait & hope that Dynamo's built-in conversion functionality will be exposed...

Test Revit nodes for Revit 2016

Quite a few changes in the Revit 2016 API - need to check which nodes need updating and/or version checks

More outputs for Triangle.SolveByPoints

• Circumcenter (center and radius)
• Orthocenter

Add unit conversion in Document.ProjectPosition

Lengths should be output als lengths, not doubles

Node compatibility for linked files

Go through all the nodes that contain a doc.GetElement() call and create an alternative version that has an additional document input in order to be able to use with linked files. Fun! Only do that for those nodes where it makes sense!!!

UV.Average

Since there's now Point.Average and Vector.Average, UV.Average would be a logical addition...

Comeback for ToDSType()

Bring ToDSType() back to Python scripts once it's been fixed:
DynamoDS/Dynamo#2460

Rework Subcategory-related nodes

Category.Subcategories and Element.SetSubcategory need to be reviewed again once Dynamo is able to handle subcategories:
DynamoDS/Dynamo#2460