[Insight-users] image memory size problems while processing connected sets based algorithms

[Luis Ibanez]

Hi David,


The documentation of this filter suggest that a better implementation
is certainly possible:


<quote>
This filter uses some dodgy coding practices - most notably copying
the image data to a linear buffer to allow direct implementation of the
published algorithm. It should therefore be quite a good candidate to
carry out tests of itk iterator performance with randomish access patterns.
</quote>



If your purpose is to remove objects that are smaller than a certain size
(in number of pixels inside the object), you could achieve this by using
the sequence of filters:


   - itkConnectedComponentImageFilter
   - itkRelabelComponentImageFilter


and calling in the second one, the method:

          SetMinimumObjectSize()


This should work in N-dimensions.


Regards,


      Luis



---------------------------------------------------------------------------------------------
On Wed, Aug 12, 2009 at 11:55 AM, David Pastor <david.pastor at die.upm.es>wrote:

>  Hello,
>
> I'm trying to run the itk::AreaOpeningImageFilter< InputImageType,
> InputImageType > on 4d images, but it does not accept many steps (actually
> less than 5). The same happens with the ConnectedTree package.
>
> Is there any way to increase the capacity of these filters?
>
> Thanks a lot!
>
> David
>
> _____________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-users/attachments/20090815/bb95733a/attachment.htm>