[Insight-users] FastMarchingImageFilter

[Lydia Ng]

Hi Mathias,

You are correct in your summation that the FastMarchingImageFilter does
not have methods for=20
- specifying the output origin or spacing
- specifying the starting index of the output region

Thanks for the bug report and we'll look into it.

Thanks,
Lydia

> -----Original Message-----
> From: Mathias Seitel [mailto:mathias . seitel at igd . fhg . de]
> Sent: Wednesday, July 30, 2003 6:07 AM
> To: ITK Mailing List
> Subject: [Insight-users] FastMarchingImageFilter
>=20
> Hi all,
>=20
> 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 !=3D (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.
>=20
> 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.
>=20
> Am I missing something?
>=20
> Thanks,
> Mathias
>=20
>=20
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk . org
> http://www . itk . org/mailman/listinfo/insight-users