[Insight-developers] Questions about importing.

[Miller, James V (Research)]

The filter is implemented using the ImportImageContainer. So the only
difference is "ease of use".  The choice of which to use typically comes
down to whether you want to view the import interface at the "data" level
or at the "filter" level.  In the past, I have taken the "data" view when
interfacing into hardware and have taken the "filter" view when interfacing
to software.  But again, it is dealers choice.  The only reason for having
both options is that you cannot do the ImportImageFilter without having
an ImportImageContainer.  

(On the historical side, the ImportImageContainer used to be seldom used.  
By default, images used a different container.  But we eliminated the 
other container and the the ImportImageContainer is the default container
used to hold pixel data.)



> -----Original Message-----
> From: Mark Foskey [mailto:mark_foskey@unc.edu]
> Sent: Monday, March 17, 2003 4:28 PM
> To: insight-developers@public.kitware.com
> Subject: [Insight-developers] Questions about importing.
> 
> 
> In the ImportImageFilter class, why is there not a SetImportPointer() 
> method that takes a const pointer for the import buffer?  
> Since most of 
> our filters are not in-place, the data will typically not be modified 
> anyway -- am I right?
> 
> Also, what kind of situation favors using an ImportImageContainer 
> rather than an ImportImageFilter, and vice versa?  My gut reaction is 
> to use the Filter when possible, since it's the ITK Way, but I don't 
> have a sense for what would require the Container, or conversely what 
> you give up by using it instead of the filter.
> 
> -- 
> Mark Foskey    (919) 843-5436  Computer-Aided Diagnosis and 
> Display Lab
> mark_foskey@unc.edu            Department of Radiology, CB 7515, UNC
> http://www.cs.unc.edu/~foskey  Chapel Hill, NC  27599-7515
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers
>