conductor.houdini.hda.driver_ui module

Access information about the connected driver inputs.

This module is only applicable to the Conductor::job node, not the Conductor::submitter node, whose inputs are jobs.

conductor.houdini.hda.driver_ui.DRIVER_TYPES

A mapping of information about input

Type:dict

driver ROPs. human_name is used in the UI, and output_parm

is used in the output_directory expression.

conductor.houdini.hda.driver_ui.get_driver_node(node)

Get connected driver node or None.

conductor.houdini.hda.driver_ui.get_driver_type(node)

Get the connected type name.

conductor.houdini.hda.driver_ui.human_name(input_type)

Human readable name for the UI.

Example: ifd becomes Mantra render, dop becomes Simulation.

conductor.houdini.hda.driver_ui.is_simulation(input_type)

Is the source node to be treated as a simulation?

This means the frame range will not be split into chunks and no frame spec UI will be shown.

conductor.houdini.hda.driver_ui.output_parm(input_type)

Name of the parameter that holds the output path.

The name is different for each type of Rop node, so we need to look it up in a map.

conductor.houdini.hda.driver_ui.update_input_node(node)

Callback triggered every time a connection is made/broken.

We update UI in 2 ways:

1. Show the type and the path to the input node.
2. Remove the frame range override section if the node is a simulation.

While it may be possible that a user wants to sim an irregular set of frames, it is very unlikely and only serves to clutter the UI.