Houdini 20.0 Executing tasks with PDG/TOPs pdg

pdg.regenerateReason module

Enumeration of possible reasons for a node to regenerate during the cook

Values

pdg.regenerateReason.Always

The node is configured to always regenerate, so it will do so because of that option. If the node is regenerating work items for a different reason it will take priority over this enum entry.

pdg.regenerateReason.Dirty

The node needs to completely dirty itself during regeneration and produce new work items.

pdg.regenerateReason.DirtyInvalidate

The same as Dirty, except work items added to the node on the new cook will automatically have their cache files invalidated and are forced to recreate them.

pdg.regenerateReason.Full

Something about the node itself has changed, e.g. a parm and the node needs to be regenerated.

pdg.regenerateReason.Propagate

Same as Full, except that if PDG encounters this regeneration status on a node it will also ensure that all outputs are upgraded to the same status if they're set to None.

pdg.regenerateReason.None

The node is not regenerating at all, and its input nodes have also not been invalidated.

pdg

attributes

cooking

data

debugging

events

exceptions

  • pdg.AttribError

    Generic exception raised when an error occurs when accessing work item attributes

  • pdg.CookError

    Generic exception raised when an error running the graph.

  • pdg.ServiceError

    Generic exception raised when an error occurs during a PDG service manager operation

expressions

  • pdg.EvaluationContext

    A module with global functions that operate on the thread-local evaluation context

internal

nodes

schedulers

services

types

workitems