[Insight-users] FastMarchingImageFilter

[Mathias Seitel]

Hi all,

FastMarchingImageFilter produces an initial level set, the size of which 
can be set manually. When using it as input for e.g. 
GeodesicActiveContoursImageFilter, along with a feature image of the 
same size a problem seems to occur if
1) the feature image has an image index != (0, 0, 0) in 3D or,
2) the feature image origin and spacing are not (0.0, 0.0, 0.0) and 
(1.0, 1.0, 1.0), respectively.

In particular, there are no methods in FastMarchingImageFilter for 
setting index, origin and spacing of the output image manually. The 
output of FastMarchingImageFilter could be corrected accordingly, by 
explicitly setting the missing values. However, this does not work when 
Update() is called on a subsequent filter in the filter pipeline, since 
in this case the output of the filter is only an intermediate step and 
cannot be intercepted by the user.

Am I missing something?

Thanks,
Mathias