andydandy74 / clockworkfordynamo Goto Github PK

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.

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.

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

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

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

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

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!!!

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

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

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

Add some alternatives:

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

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.

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

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

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

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

• Circumcenter (center and radius)
• Orthocenter

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

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

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

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

• 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

Check if these make sense at all in 0.7:

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

need that node!

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

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.

• ComponentLayoutForCNC
• HarvestDome

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

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

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

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

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

would be useful...

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

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

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

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

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!

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

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

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

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

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

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.

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

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

Test this with SunDirectionToPanels workflow

Lengths should be output als lengths, not doubles

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

"only on top of Revit" etc.