Deadline, Houdini, Python, Scripting

ns_Startup & Deadline Scripts


This python script was created to starting Houdini easily with the right workgroups/renderers etc.
Done with PyQt4. Including a WOL functionality for my NAS and a preset/job system.
I also modified my Thinkbox Deadline submission scripts to handle variable environments & the proper Houdini version on my “Renderfarm”….2 Clients.

Right now i can start Arnold & Redshift from a workgroup location. I implement also a checkup function to my ns_Version plugin for houdini. The checkup starts with the 456.py script and guaranteed the right environments for my projects. I implemented a update function per robocopy as well, to keep all up to date over all workstations.

(ns_Version – ENV Checkup and deadline scripts enhancements down below).

 

ns_Version – ENV Checkup per project inside Houdini. (You can see, the project was original created with Houdini 16.0.736 and with a lower Redshift version).

 

To pass the right environments/version through Deadline, i write out a .xml-file which is uniqe named against the render-.hip.

Common path:
C:\Users\<USER>\AppData\Local\Thinkbox\Deadline10\submitters\HoudiniSubmitter\DeadlineHoudiniClient.py

This .xml-file, i read back when hython.exe starts and setting the right enviroment/version variables, before the clients begin to render. (Two functions are modded here)

Common path:
<YOUR_DeadlineRepository>\plugins\Houdini\Houdini.py

 

In the Deadline “Configure Plugins…” Editor, i replaced the executable pathes with my <ns_version> tags.

 

 Hint:

Set HOUDINI_NO_ENV_FILE=1 to ignore user specific configurations.
More variables and descriptions find here: http://www.sidefx.com/docs/houdini/ref/env.html.

Another Hint:

Found this yesterday. Pretty good article about Houdini Environment Variables from Juraj Tomori:
Houdini tip | Taking advantage of environment variables