Revision as of 16:29, 18 November 2010

Attendees

A potential FEMMeshSpatialObject could be created
- Still a "FEMMesh" must be created
How much refactoring is needed in Numeric/FEM
IO is a critical need for FEM.
- One option is to implement a FEMMeshSpatialObject and
  - a Reader Writer for it.
    - We can take the IO code from the Solver in the registration framework (Code/Numerics/FEM/itkFEMSolver.cxx)

The actual TimeStamp will probably go in the itk::DataObject
and will be available to the SpatialObject (given that it derives from itk::DataObject)

A new filter that takes two inputs
- an Image
- an SpatialObject (as a mask)
This filter compute intensity and shape statistics from image pixels that are "inside" of the spatial object.
Use case: Having thousands of cells (biological ones) represented as itk::SpatialObjects and over each one compute statistics from the image pixels that are inside.
- Multi-thread over groups of spatial objects.
- Maybe reusing the LabelMap statistics classes ?
- Converting the spatial objects to a label map.

Kitware: to create skeletons classes
- FEMSpatialObject
- Make sure that it works nicely with the itkSpatialObjectWriter.txx (in ITK/Code/IO)

@@ Line 28: / Line 28: @@
 ** an SpatialObject (as a mask)
 * This filter compute intensity and shape statistics from image pixels that are "inside" of the spatial object.
+* '''Use case:''' Having thousands of cells (biological ones) represented as itk::SpatialObjects and over each one compute statistics from the image pixels that are inside.
+** Multi-thread over groups of spatial objects.
+** Maybe reusing the LabelMap statistics classes ?
+** Converting the spatial objects to a label map.
 = Action Items =