KWScene/Documentation/Supported Generators/VTK/Image: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 57: Line 57:
kwsVTKGenerator -> kwsVTKNodeGenerator
kwsVTKGenerator -> kwsVTKNodeGenerator
kwsVTKNodeGenerator -> kwsVTKImageNodeGenerator
kwsVTKNodeGenerator -> kwsVTKImageNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKImageNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKDICOMImageNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKDICOMImageNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKAnalyzeImageNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKAnalyzeImageNodeGenerator

Revision as of 17:05, 22 April 2010

Desired Format Support

  • DICOM (.dcm)
  • ANALYZE (.hdr/.ima)
  • XML (.vti)
  • MHA


Class Diagrams

This is a graph with borders and nodes. Maybe there is an Imagemap used so the nodes may be linking to some Pages.

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

This is a graph with borders and nodes. Maybe there is an Imagemap used so the nodes may be linking to some Pages.