ITK/Release 4/SpatialObjects/2010.11.18-Meeting: Difference between revisions
From KitwarePublic
< ITK | Release 4 | SpatialObjects
Jump to navigationJump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
= Attendees = | |||
* Arnaud Gelas | * Arnaud Gelas | ||
| Line 7: | Line 5: | ||
* Luis Ibanez | * Luis Ibanez | ||
= Potential Use for FEM = | |||
* A potential '''FEMMeshSpatialObject''' could be created | * A potential '''FEMMeshSpatialObject''' could be created | ||
Revision as of 16:19, 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)
- a Reader Writer for it.
- One option is to implement a FEMMeshSpatialObject and
Action Items
- Kitware: to create skeletons classes
- FEMSpatialObject
- Make sure that it works nicely with the itkSpatialObjectWriter.txx (in ITK/Code/IO)
