The debugger executes an apex graph and captures the intermediate port values of all nodes which were executed.
Instances of the debugger are retrieved by calling hou.ApexNode.debugger. The debugger is enabled when the apex graph is displayed in an Apex Network View and the Apex Network View has enabled the debugger (through its Debug menu). The debugger is automatically disabled whenever the network view is no longer displaying the apex graph.
Methods ¶
data(portpath)
Returns the value of the port captured by the debugger. If the debugger is not enabled, None is returned.
The portpath must be the port’s full path, along with its port kind. For example, a valid input port path take the form of /subnet/node:port[in] and a valid output port path takes the form of /subnet/node:port[out].
The string “Not Evaluated” is returned if the port’s value was not captured by the debugger. This may occur when the node does not have a downstream connection to a port on a graph’s output node (and therefore is not evaluated when executing the graph), or when the node is not being watched by the debugger.
isEnabled()
→ bool
Returns true if the debugger is enabled.
setWatchPattern(pattern)
Sets the debugger’s watch pattern, which is an apex path pattern determining which nodes' data are captured by the debugger.
The debugger only captures the port values of nodes which are included by the apex path pattern. When pattern is an empty string, all nodes are watched by the debugger.
The watch pattern can be used to improve the memory usage of the debugger. If the user is only interested in the values of a subset of nodes, the debugger will avoid capturing the values of nodes which do not match the watch pattern.
watchPattern()
→ str
Returns the watch pattern currently used by the debugger.
An empty string means that the debugger is watching all nodes in the graph.
watchPaths()
→ tuple of str
Returns a tuple of the node paths which are watched by the debugger. These are the nodes which currently match the watch pattern.
| See also |