- Have them select a node “theirnode” (filecache, ifd, rop_geometry are some likely types) they want to run on the farm
- Create a “topnet” node
- Create a “tractorscheduler” node in the topnet
- Delete the localscheduler that got created with the topnet, and set the topnet default scheduler to the tractorscheduler created above
- Create a “ropfetch” node, point “roppath” parm at “theirnode”, “framegeneration” to 1 (frame range) and turn on “Reset $HIP on cook”
- call hou.hipFile.save()
- programmatically pressButton() the topscheduler.submitjob button to submit graph as job.
This works with 17.5.460, the main PDG->Cook task on the farm job generates additional ropfetch tasks to do each output frame/item. But the same code with 18.0.460 (and a test install of the 18.0.491 daily), it doesn't. The job goes to Tractor, and the main PDG->Cook task starts up, but it doesn't create any subtasks or generate any output, and the main task finishes with output like this:
Given Node ‘farmtop’, Cooking Node ‘ropfetch_farm_torus_transform’
Finished Cook
Work Item States:
==== 2020/06/09 21:45:32 process complete, exit code: 0 ====
I'm guessing it is something about the work items or dirty flags of my topnet or ropfetch that is somehow differently initialized in 18.0 vs 17.5 where it worked. If I do this:
- Add a localscheduler to my topnet and make it the default
- Click the topnet's “Cook output node” button
- Let it start itself up, then do “Cancel Cook”
If anyone sees something obvious I should be doing in the code between creating the ropfetch node and saving the file and doing the Submit Job As Graph to get this to work again with 18.0, please let me know. I've tried assorted calls to dirtyTasks(), dirtyAllTasks() and cook() on the various topnet nodes, but haven't figured it out yet.