[Insight-users] Quick Q: Boundary Behavior of NeighborhoodIterator in ThreadedGenerateData?

[Cory Quammen]

Kent,

The boundary condition is invoked at the full image boundary, not the
boundary of the region for the thread.

Cory

On Thu, Aug 18, 2011 at 4:00 PM, kent williams
<nkwmailinglists at gmail.com> wrote:
> I'm working on multi-threading a filter, and have a question about what
> happens with NeighborhoodIterators.
>
> When you're inside ThreadedGenerateData, you're operationg on the pixels
> in the outputRegionForThread.
>
> If I set up a neighborhood iterator on the input to the filter thusly:
>
>  ConstNeighborhoodIterator<InputImageType> it(
> m_NeighborhoodRadius,inputImage,outputRegionForThread );
>
> Does the Neighborhood Iterator see a boundary at the edge of the entire
> input image, or at the edge of the thread's region?
> _____________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://www.kitware.com/products/protraining.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-users
>



-- 
Cory Quammen
Research Associate
Department of Computer Science
The University of North Carolina at Chapel Hill