Pipeline IDs: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
| Line 12: | Line 12: | ||
===Source ID=== | ===Source ID=== | ||
A source ID is a unique identifier for a data object that resides in source data (either a file, a stream, or a source filter). For example, Exodus contains a GlobalElementID. | |||
<i>Requirement</i> If the input data contains an identifier for an object, this data is | |||
retrieved from the file as the Source ID. | |||
=== | ===Other IDs=== | ||
If the <b>Pipeline ID</b> and the <b>Source ID</b> are not sufficient, a filter may create its own named ID. It may not overwrite other ID types. | |||
Revision as of 12:46, 10 January 2006
Overview
Currently, there is no native support for unique identifiers in vtk/ParaView. There are many issues that relate to this.
Proposal
Pedigree ID
A pedigree ID is defined as the ID which relates input objects to output objects. It is used to follow the 'pedigree' of an object. This ID is applied by a filter, in a way defined by its operation. Two examples illustrate its use.
Requirement A Pedigree ID is copied from parent to child. Any filter that creates cells that have a parent/child relationship should copy the Pedigree ID appropriately.
Source ID
A source ID is a unique identifier for a data object that resides in source data (either a file, a stream, or a source filter). For example, Exodus contains a GlobalElementID.
Requirement If the input data contains an identifier for an object, this data is retrieved from the file as the Source ID.
Other IDs
If the Pipeline ID and the Source ID are not sufficient, a filter may create its own named ID. It may not overwrite other ID types.
