On this page |
Overview ¶
Work items track results created by the item in the output
attribute. The results are strings, usually file paths to files created by the work item. All results are tagged with a “tag” string that describes the type of the result. The tag string is a hierarchy of broad types down to more specific types, separated by slashes (similar to MIME types but totally free-form). For example:
Tag |
Description |
---|---|
|
Geometry file |
|
Terrain geometry file |
|
Geometry file containing a building |
Some nodes and API functions let you match files by their tag. Tag matching is by prefix, so a file tagged as file/geo/terrain
will match both file/geo
and file
, but not file/geo/building
.
Although work item outputs are typically files, it is possible to have other types of information reported back as a result. For example, when using the ROP Fetch to cook a distributed simulation, the sim tracker work item will report a socket/ip
and socket/port
result, which other work item can use to connect to the tracker.
Tagging results ¶
-
Nodes that generate files usually have a parameter for specifying how to tag work item results. The default tag is usually set based on the intended use of that node.
For example, the Geometry Import lets you cook a SOP network and write the result to a geometry file on disk. The node has a Result tag parameter that sets the tag for the generated file. The default tag is
file/geo
.