|
VTK
|
The VTK pipeline relies on algorithms providing information about their input and output and responding to requests. More...
The VTK pipeline relies on algorithms providing information about their input and output and responding to requests.
The information objects used to perform these actions map known keys to values. This is a list of keys that information objects use and what each key should be used for.
|
static |
Keys used to specify input port requirements.
|
static |
|
static |
|
static |
|
static |
|
static |
|
static |
|
static |
This key tells the executive that a particular output port is capable of producing an arbitrary subextent of the whole extent.
Many image sources and readers fall into this category but some such as the legacy structured data readers cannot support this feature.
|
static |
Key that tells the pipeline that a particular algorithm can or cannot handle piece request.
If a filter cannot handle piece requests and is asked for a piece, the executive will flag an error. If a structured data source cannot handle piece requests but can produce sub-extents (CAN_PRODUCE_SUB_EXTENT), the executive will use an extent translator to split the extent into pieces. Otherwise, if a source cannot handle piece requests, the executive will ask for the whole data for piece 0 and not execute the source for other pieces.
|
static |
Key defining a request to make sure the output data objects exist.
|
static |
Key defining a request to make sure the output information is up to date.
|
static |
Key defining a request to make sure the output data are up to date.
|
static |
Key defining a request to mark outputs that will NOT be generated during a REQUEST_DATA.
|
static |
Key to specify in pipeline information the request that data be released after it is used.
|
static |
Key to store a mark for an output that will not be generated.
Algorithms use this to tell the executive that they will not generate certain outputs for a REQUEST_DATA.
|
static |
Key defining a request to propagate the update extent upstream.
|
static |
Key defining a request to propagate the update extent upstream.
|
static |
Key defining a request to make sure the meta information is up to date.
|
static |
Key for an algorithm to store in a request to tell this executive to keep executing it.
|
static |
Keys to store an update request in pipeline information.
|
static |
|
static |
|
static |
|
static |
|
static |
Key for combining the update extents requested by all consumers, so that the final extent that is produced satisfies all consumers.
|
static |
Key to store the whole extent provided in pipeline information.
|
static |
This is set if the update extent is not restricted to the whole extent, for sources that can generate an extent of any requested size.
|
static |
Key to specify the request for exact extent in pipeline information.
|
static |
Key to store available time steps.
|
static |
Key to store available time range for continuous sources.
|
static |
Update time steps requested by the pipeline.
|
static |
Whether there are time dependent meta information if there is, the pipeline will perform two extra passes to gather the time dependent information.
|
static |
key to record the bounds of a dataset.
|
staticprotected |
Keep track of the update time request corresponding to the previous executing.
If the previous update request did not correspond to an existing time step and the reader chose a time step with it's own logic, the data time step will be different than the request. If the same time step is requested again, there is no need to re-execute the algorithm. We know that it does not have this time step.
1.8.11