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

From KitwarePublic
Jump to navigationJump to search
Line 16: Line 16:
*** 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)
= Action Items =
* Kitware: to create skeletons classes
** FEMSpatialObject
** Make sure that it works nicely with the itkSpatialObjectWriter.txx (in ITK/Code/IO)

Revision as of 16:19, 18 November 2010

Spatial Objects

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)

Action Items

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