KWScene/Documentation/Supported Generators/VTK/Image: Difference between revisions
From KitwarePublic
< KWScene | Documentation | Supported Generators | VTK
Jump to navigationJump to search
No edit summary |
|||
Line 57: | Line 57: | ||
kwsVTKGenerator -> kwsVTKNodeGenerator | kwsVTKGenerator -> kwsVTKNodeGenerator | ||
kwsVTKNodeGenerator -> kwsVTKImageNodeGenerator | kwsVTKNodeGenerator -> kwsVTKImageNodeGenerator | ||
kwsVTKImageNodeGenerator -> kwsVTKImageNodeGenerator | |||
kwsVTKImageNodeGenerator -> kwsVTKDICOMImageNodeGenerator | |||
kwsVTKImageNodeGenerator -> kwsVTKAnalyzeImageNodeGenerator | |||
kwsVTKImageNodeGenerator -> kwsVTKXMLImageNodeNodeGenerator | |||
} | } | ||
</graphviz> | </graphviz> |
Revision as of 17:04, 22 April 2010
Desired Format Support
- DICOM (.dcm)
- ANALYZE (.hdr/.ima)
- XML (.vti)
- MHA
Class Diagrams
Options
Option A
- Create a KWScene hierarchy that uses vtkDICOMImage, Analyze, XML Readers for 3D images, and vtkImageReader2 (& Factory) for 2D images.
- Will have classes
- ImageNode-KWSGenerator
- DICOMImageNode-KWSGenerator
- AnalyzeImageNode-KWSGenerator
- XMLImageNode-KWSGenerator
- Classes deriving from kwNodeGenerator will implement a virtual method
- AlgorithmPointer InstantiateNodeReader()
- Unlike SurfaceNode, ConnectToRenderer does not do anything.
Proposed Hierarchy