Hi Burlen,
There is support for this in the pipeline. In the appropriate pipeline pass
(REQUEST_INFORMATION, REQUEST_UPDATE_EXTENT ro
REQUEST_DATA), add the keys you want copied to the request object
(the first argument to ProcessRequest) under the KEYS_TO_COPY key.
This will tell the executive
Thanks, it worked!
On 05/06/2011 06:00 AM, Berk Geveci wrote:
Hi Burlen,
There is support for this in the pipeline. In the appropriate pipeline pass
(REQUEST_INFORMATION, REQUEST_UPDATE_EXTENT ro
REQUEST_DATA), add the keys you want copied to the request object
(the first argument to
Burlen,
Keys are not propagated by pipeline by default. So your approach would
only work when there's no other filter between the reader and your
filters. With ParaView 3.10, vtkPVPostFilter get inserted always into
the pipeline after every algorithm. As a result your keys maybe
getting eaten up
Hi Utkarsh,
Yes, I had connected the reader or source directly to the filter with no
other filters intervening.
I have used the keys for a number of things. In addition to passing meta
data I also implemented dynamic load balancing in a couple of algorithms
by passing vtkObjects. For
Hi All,
I have a reader that gets the information object from it's output and
adds some keys for downstream filters to use. This recently stopped
working with version 3.10. Can anyone shed some light on what might have
caused the change in behavior in version 3.10? Was this a deliberate
