|On this page|
You can use this node to create work items for nodes that match a pattern. The node uses the same pattern matching logic as the network editor’s Find window. For example, the pattern
box* matches nodes that begin with the name
The names, paths, category, and node type for each matched node are stored as attributes on the work items produced by this node.
The pattern is applied relative to a root node, is specified using the Root Node parameter, and can be applied recursively to child nodes.
The operator type category name. For example, SOP or TOP.
The name of the node. For example,
The full path to the node. For example,
The name of the node’s operator type. For example, torus or box.
Determines when this node will generate work items. You should generally leave this set to “Automatic” unless you know the node requires a specific generation mode, or that the work items need to be generated dynamically.
All Upstream Items are Generated
This node will generate work items once all of the input nodes have generated their work items.
All Upstream Items are Cooked
This node will generate work items once all of the input nodes have cooked their work items.
Each Upstream Item is Cooked
This node will generate work items each time a work item in an input node is cooked.
The generation mode is selected based on the generation mode of the input nodes. If any of the input nodes are generating work items when their inputs cook, this node will be set to Each Upstream Item is Cooked. Otherwise, it will be set to All Upstream Items are Generated.
Specifies the root node that the Node Pattern is applied to.
Specifies the pattern to use when matching nodes. This parameter uses the same pattern matching logic as the network editor’s Find window.
Sort Nodes By
Determines how the list of nodes is sorted.
The nodes are left unsorted. When a specific order is not needed, this option is marginally faster because it doesn’t need to sort the list of matched nodes.
The nodes are sorted alphabetically by name. It is possible for multiple nodes to have the same name. For example, like when the nodes are in different subnets and Recursive is on. In this case, it would probably be more appropriate to use sort by Node Path since the node path is always unique.
The nodes are sorted alphabetically based on their full file path.
When on, the pattern is applied recursively to subnets inside of the root node.
Split Results into Separate Work Items
When on, one work item is created for each matching node. When off, a single work item with all node paths is created.
Inherit Upstream Work Item Index
When Split Files into Separate Items and this parameter are both on, generated work items will inherit their upstream work items' indices. When this parameter is off and Split Files into Separate Items is on, the work items' indices are based on the node’s position within the list of matched nodes.