[Insight-developers] PhysicalObject & SpatialFunction
Luis Ibanez
ibanez@cs.unc.edu
Tue, 27 Nov 2001 09:34:02 -0500
Hi,
The overlap is apparent. In fact PhysicalObject is
internally using the SpatialFunction classes created
by Damion. It is a similar case to what happened with the
vnl_optimizers and the itkOptimizers.
The SpatialFunction classes provide the core functionality
for the PhysicalObject when it comes to test if a point
is inside or outside the object.
PhysicalObjects are intended to provide extended
functionality like for example create and maintain an
itkMesh around its border. PhysicalObjects are the base
for ModelShape segmentation and registration.
PhysicalObjects are oriented to support processes like:
- creating a "generic" kidney 3D model shape that can
be registered with an image and then deformed
in order to better fit the image content
- defining anatomical context for image analysis:
e.g. when looking for a Liver in a CT we can start by
identifying the spine, place a 3D model there, then move
on to identifying the ribs and place rib 3D models there,
.... and so on. It is well known that radiolgist identify
structures by their context. e.g something it may look like
a liver... but it if not in the right place it should not
be a liver.
SpatialFunction are more low level classes providing a very
efficient implementation for testing in/out regions.
PhysicalObject is intended to provide a framework for a high
level representation of objects that have anatomical meaning.
We anticipate to create an itkLiverShape class.... for example.
Luis
========================================
George Stetten wrote:
>
> Hi Stephen,
>
> I think there may be overlap with what Damion has been developing. We
> create basic shapes already which we use to calibrate shape recognition and
> measurement algorithms.
>
> George
>