KWScene/Documentation/Supported Generators/ITK/Image: Difference between revisions
From KitwarePublic
< KWScene | Documentation | Supported Generators | ITK
Jump to navigationJump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Desired Format Support = | = Desired Format Support = | ||
DICOM (.dcm) | ** DICOM (.dcm) | ||
Analyze (.hdr/.ima) | ** Analyze (.hdr/.ima) | ||
XML (.vti) | ** XML (.vti) | ||
** MetaImage (.mha) | |||
= Class Diagrams = | = Class Diagrams = | ||
| Line 33: | Line 34: | ||
== Option A == | == Option A == | ||
* Create a KWScene hierarchy where | * Create a KWScene hierarchy where FactoryBasedImageGenerator handles all relevant file formats. | ||
* Will have classes | * Will have classes | ||
** | ** FactoryBasedImage-KWSGenerator, which can generate either | ||
** an image of most single-file types via itk::ImageIOFactory or | ** an image of most single-file types via itk::ImageIOFactory or | ||
** an Image Series via itk::GDCMImageIO. | ** an Image Series via itk::GDCMImageIO. | ||
** because of the breadth and reliability of ImageIOFactory. | ** because of the breadth and reliability of ImageIOFactory. | ||
** ImageNodeGenerator is | ** ImageNodeGenerator is the base class here, to be consistent with nomenclature in VTK. | ||
=== Proposed Hierarchy === | === Proposed Hierarchy === | ||
| Line 48: | Line 49: | ||
kwsITKNodeGenerator | kwsITKNodeGenerator | ||
kwsITKImageNodeGenerator | kwsITKImageNodeGenerator | ||
kwsITKFactoryBasedImageNodeGenerator | |||
kwsITKGenerator -> kwsITKNodeGenerator | kwsITKGenerator -> kwsITKNodeGenerator | ||
kwsITKNodeGenerator -> kwsITKImageNodeGenerator | kwsITKNodeGenerator -> kwsITKImageNodeGenerator | ||
kwsITKImageNodeGenerator-> kwsITKFactoryBasedImageNodeGenerator | |||
} | } | ||
</graphviz> | </graphviz> | ||
Latest revision as of 19:32, 22 April 2010
Desired Format Support
- DICOM (.dcm)
- Analyze (.hdr/.ima)
- XML (.vti)
- MetaImage (.mha)
Class Diagrams
Options
Option A
- Create a KWScene hierarchy where FactoryBasedImageGenerator handles all relevant file formats.
- Will have classes
- FactoryBasedImage-KWSGenerator, which can generate either
- an image of most single-file types via itk::ImageIOFactory or
- an Image Series via itk::GDCMImageIO.
- because of the breadth and reliability of ImageIOFactory.
- ImageNodeGenerator is the base class here, to be consistent with nomenclature in VTK.
Proposed Hierarchy
