KWScene/Documentation/Supported Generators/ITK/Image: Difference between revisions
From KitwarePublic
< KWScene | Documentation | Supported Generators | ITK
Jump to navigationJump to search
Line 33: | Line 33: | ||
== Option A == | == Option A == | ||
* Create a KWScene hierarchy where ImageGenerator handles all | * Create a KWScene hierarchy where ImageGenerator handles all relevant file formats. | ||
* Will have classes | * Will have classes | ||
** Image-KWSGenerator, which can generate either an image of most single-file types via itk::ImageIOFactory | ** Image-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. | |||
** ImageNode is not an abstract class here, and can handle any image. | |||
=== Proposed Hierarchy === | === Proposed Hierarchy === |
Revision as of 18:53, 22 April 2010
Desired Format Support
DICOM (.dcm) Analyze (.hdr/.ima) XML (.vti)
Class Diagrams
Options
Option A
- Create a KWScene hierarchy where ImageGenerator handles all relevant file formats.
- Will have classes
- Image-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.
- ImageNode is not an abstract class here, and can handle any image.
Proposed Hierarchy