Agenda&Status 091908: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
|||
Line 46: | Line 46: | ||
* Lesion Sizing Toolkit | * Lesion Sizing Toolkit | ||
** http://public.kitware.com/LesionSizingKit | ** http://public.kitware.com/LesionSizingKit | ||
Revision as of 12:06, 19 September 2008
FIFTH MEETING IN SECOND LIFE
Project Management
- ITK 3.10 : Release Schedule
- http://www.itk.org/Wiki/ITK_Release_Schedule#Release_3.10_Schedule
- End of October ??
- What to include ?
- QuadEdgeMesh & New processing filters in the Insight Journal
Technical Topics
- Enabling itk::Image to behave as itk::OrientedImage
- CMake flag is ON in several machines (Zion & Redwall)
- Making it ON by default ?
- Removing the flag ?
- Performance changes ?
- ImageIO support for GUI
- ImageIO API for GUI Support PROPOSAL PAGE
- ImageIO classes should report
- The extensions that they support
- A description for each extension
- A generic name for the file format ?
- Currently the ImageIO classes have methods
- ArrayOfExtensionsType GetSupportedWriteExtensions() const
- ArrayOfExtensionsType GetSupportedReadExtensions() const
- void AddSupportedWriteExtension( const char * extension )
- void AddSupportedReadExtension( const char * extension )
- Questions
- How to deal with Analyze and Nifti
- How to deal with DICOM (no specific extension)
- Proposals
- Proposal 1
- Change the GetSupportedWriteExtensions() and GetSupportedReadExtensions() to return an array of pairs (extension, description)
- Add a method to return a generic description of the ImageIO (e.g. NIFTI, Analyze, MetaImage)
- Proposal 2
- Change the GetSupportedWriteExtensions() and GetSupportedReadExtensions() to return an array of triplets (extension, description,generic description)
- Proposal 1
- Oriented Images
- Lesion Sizing Toolkit