|On this page|
This node can be used to cook a different TOP network. The other network can exist in the same .hip file or an external file, and will be cooked via the active scheduler. The other TOP network is evaluated in a separate process from the current one.
This node works in two steps. First work items are generated to cook the external
TOP network referred to by the TOP Path parameter. The attributes and input
files associated with each work in this node are made accessible to the fetched
network using the standard work item JSON format. The path to the JSON file is
$PDG_FETCH_JSON_FILE in the environment used to cook the fetched
network. The fetched network can use a TOP Fetch Input
node to load that work item into its own network.
When the remote TOP network is cooked, the work items on the output node of that network are saved to disk and reported back to PDG. Then these items are re-created in the topfetch node. The items visible on the topfetch node are those re-created items.
Work Item Generation
Whether this node generates static or dynamic work items. You should generally leave this set to "Automatic" unless you know the node’s work items can be computed statically, or that they need to be generated dynamically.
This node always creates dynamic work items: it waits until the upstream work items are known, and generates new work items from the upstream work items.
This node always creates static work items: it creates the number of work items it thinks it needs based on the parameters (and any upstream static items) before the network runs.
If the input is static (a static processor, or a partitioner with only static inputs, or a mapper), this node generates static work items, otherwise it generates dynamic work items.
The path to the TOP network within the .hip file specified in the Hip File Path parameter.
Hip File Path
The path to the .hip file that contains the TOP network to fetch.