[Insight-users] setRequestRegion + ConnectedComponent filter

[jerome schmid]

Hi James,

I haven't noticed this point at the beginning, and as the thresholding
worked I didn't understand...! I think that some times it is better to
perform CC analysis locally because you save a *lot* of time, even if you
have to be aware of boundary components...

Thanks!

Regards,

Jerome

-----Message d'origine-----
De : Miller, James V (Research) [mailto:millerjv at crd.ge.com]
Envoyé : lundi 7 juin 2004 19:30
À : 'jerome schmid'; insight-users at itk.org
Objet : RE: [Insight-users] setRequestRegion + ConnectedComponent filter


ConnectedComponents needs the entire input inorder to ensure the
components within your initial requested region are properly labelled.
A component could leave your initial requested region and loop back
into the region on (perhaps) another boundary). In the process of
calculating
the region you request, the algorithm has to label every pixel in the
image anyway, so it just outputs everything.

If you only want to label objects within a region, and you are confident
that an object does not leave the region and re-enter, then you'll need
to use ExtractImageFilter or RegionOfInterestImageFilter prior to running
the connected components.

Jim