Top To Chop not cooking

Hi,

I’m experiencing an issue where the toptochops aren’t cooking/updating if they are not connected to something that “makes use” of the data.
I have a script that tries to access the toptochops but sometimes the values don’t update…
is this expected or am I doing something wrong?

Yes, this is expected. See
docs.derivative.ca/index.php?title=Cook
for details on when things cook. If your script is accessing the data then the values should be up-to-date, because the CHOP should cook when the values are requested. Please post an example if you think the behaviour is not as expected.

It makes total sense, I guess I’m just surprised that a request to a component’s values via python doesn’t trigger the cook automatically.

I resorted to force the cooking.

that said, the cooking time on the initial toptochop cook is extremely long (~3 seconds for a full FHD image)

If you haven’t done so yet, you can set the download type parameter on the TOP to CHOP to “Next frame (fast)” for a speedup.

thanks @nettoyeur, I tried that already. it is fairly fast after the initial population of values in the first cook. the problem is only the first cook, which freezes the network for (what feels like) an eternity…

Requesting the values of a node should cook the node if the node is needs cooking. You’ll have to post an example for us to know if it is a bug or not.