[Insight-users] InputRequestedRegion for filter with mini-pipeline

[Miller, James V (Research)]

Nils, 

When a filter uses a mini-pipeline, that filter is responsible for provided an 
appropriate GenerateInputRequestedRegion that encapsulates the needs of the mini-pipeline.

If a GenerateInputRequestedRegion is not provided, then the outer pipeline will initially
request an input region that matches the size of the output region.  Then when the 
mini-pipeline runs, it may need additional input, forcing the upstream pipeline to 
re-execute. It will all "work" but the upstream pipeline will execute more times
than it needs to.

Jim



-----Original Message-----
From: insight-users-bounces+millerjv=crd.ge.com at itk.org
[mailto:insight-users-bounces+millerjv=crd.ge.com at itk.org]On Behalf Of
Nils H. Busch
Sent: Thursday, May 26, 2005 7:42 AM
To: insight-users at itk.org
Subject: [Insight-users] InputRequestedRegion for filter with
mini-pipeline


Hi,

do I need to override the GenerateInputRequestedRegion for a filter using
a mini-pipeline with multiple inputs. One of the filters in the
mini-pipeline is a sub-class of FiniteDifferenceImageFilter. Do I need to
pad the input region for the input of this filter in its enclosing filter
or will this be done automatically ? More generally, my question touches
the issue if or in which cases a filter containing a mini-pipeline needs
to override GenerateInputRequestedRegion etc or if the pipeline handles
this automatically  and hence it is a bad idea to try to set them
explicitly.

Any pointers to manual sections or example code are greatly appreciated.

Thanks.
-- 
  Nils H. Busch
_______________________________________________
Insight-users mailing list
Insight-users at itk.org
http://www.itk.org/mailman/listinfo/insight-users