Dynamo: request the feature of setting; Force re-calculation mode

Created on 20 Jun 2016 · 12Comments · Source: DynamoDS/Dynamo

Dynamo version

Dynamo 1.0.0.1180

Operating system

Windows 10 and 7

Dynamo node seems saves it's calculated result as a cache. And it prevents from re-running from same input.
But dynamo can't see an update of related application such as Revit so this cache mechanism sometimes acts on the dangerous side for system.
It would be better that there is a setting to run whole node every time.

Thank and regards,
Yoji Takahashi

Source

birdland007s

👍1

Most helpful comment

@ikeough I've got some 😜

interacting with an API that provides no events on document or element modification.
when you have gotten into a strange state with an API that does provide events and do not wish to close and re-open Dynamo, but you want to be sure of the state that you are in.
When your graph is dependent on a root node that is a random number but which will never re-execute because the live-runner cannot anticipate its need to re-execute. (run periodic is a bad solution here, though I guess a node author should dirty this kind of node somehow).
when you are using a python node that does things like web requests internally or generates random numbers and should re-run.
I'll think of some more.

mjkkirschner on 21 Jun 2016

👍4

All 12 comments

hi @birdland007s , actually there is an option to do that, though it doesn't execute all nodes _every time_. If the run mode is switched to Manual, you can force Dynamo to run all nodes through this menu item:

untitled

ke-yu on 21 Jun 2016

but you'll have to build from source and use sandbox to use this option I think?

mjkkirschner on 21 Jun 2016

This is by design. We enable third parties to create libraries which force re-execution. But it is not the preferred mode for execution. @birdland007s, can you give an example where you need to force a reexecution of a node?

ikeough on 21 Jun 2016

@ikeough I've got some 😜

interacting with an API that provides no events on document or element modification.
when you have gotten into a strange state with an API that does provide events and do not wish to close and re-open Dynamo, but you want to be sure of the state that you are in.
When your graph is dependent on a root node that is a random number but which will never re-execute because the live-runner cannot anticipate its need to re-execute. (run periodic is a bad solution here, though I guess a node author should dirty this kind of node somehow).
when you are using a python node that does things like web requests internally or generates random numbers and should re-run.
I'll think of some more.

mjkkirschner on 21 Jun 2016

👍4

Thanks all and sorry for this late replay.
@ikeough, the node, which I want to re-execute eveytime, is Python Script.
The script reads Revit objects and gets their attributes.
The attributes is cooked after that following nodes.

I can understand this is by design, that is, it is difficult to always re-execute in the situation which Dynamo works together with unspecified apps. But I also think it is possible to implement re-execution mode as standard function on the limited condition and nodes. It is enough for me that re-executed nodes are only user specified node and Manual mode.

Best regards,
Yoji

birdland007s on 23 Jun 2016

Also see #3273 & #4603

andydandy74 on 23 Jun 2016

@mjkkirschner I believe we can add this through a method attribute. Something like [AlwaysReexecute].

ikeough on 23 Jun 2016

exactly what I was thinking!

mjkkirschner on 23 Jun 2016

@birdland007s We will need to do some design to provide a way for the python node to continually re-execute. I do not want to add continuous re-execution to the python node, by default because the python node gives you the power to write a script to do anything including long-running operations that you don't want to execute every time if you can avoid it.

The end result would be similar to some improvements to the python node requested in #3378, regarding using comments in the python node to trigger certain functionality.

ikeough on 23 Jun 2016

Agree with you and the list of #3378.
Thanks a lot.

birdland007s on 23 Jun 2016

@ikeough @mjkkirschner is it possible to hash the code inside the Python node and execute it if only there has been changes from the last run? Having it to always re-run is not going to be efficient.