ITK/Release 4/SpatialObjects/2010.11.18-Meeting: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
Line 14: Line 14:
*** a Reader Writer for it.
*** a Reader Writer for it.
**** We can take the IO code from the Solver in the registration framework (Code/Numerics/FEM/itkFEMSolver.cxx)
**** We can take the IO code from the Solver in the registration framework (Code/Numerics/FEM/itkFEMSolver.cxx)
= Other Modifications =
== Add TimeStamp ==
* The actual TimeStamp will probably go in the itk::DataObject
* and will be available to the SpatialObject (given that it derives from itk::DataObject)
== Compute Statistics ==
* 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.


= Action Items =
= Action Items =

Revision as of 16:24, 18 November 2010

Attendees

  • Arnaud Gelas
  • Vincent Magnotta
  • Luis Ibanez

Potential Use for FEM

  • 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)

Other Modifications

Add TimeStamp

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

Compute Statistics

  • 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.

Action Items

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