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

From KitwarePublic
Jump to navigationJump to search
Line 24: Line 24:
vtkAlgorithm -> vtkImageAlgorithm  
vtkAlgorithm -> vtkImageAlgorithm  
vtkImageAlgorithm -> vtkImageReader2
vtkImageAlgorithm -> vtkImageReader2
vtkImageReader2 -> vtkMetaImageReader
vtkImageReader2 -> vtkDICOMImageReader
vtkImageReader2 -> vtkDICOMImageReader
vtkImageReader2 -> vtkAnalyzeReader
vtkImageReader2 -> vtkAnalyzeReader
vtkImageReader2 -> vtkMetaImageReader
vtkAlgorithm -> vtkXMLReader
vtkAlgorithm -> vtkXMLReader
vtkXMLReader -> vtkXMLDataReader
vtkXMLReader -> vtkXMLDataReader

Revision as of 17:07, 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
    • FactoryBasedImageNode-KWSGenerator
    • DICOMImageNode-KWSGenerator
    • AnalyzeImageNode-KWSGenerator
    • XMLImageNode-KWSGenerator
  • Classes deriving from kwsImageNodeGenerator 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.

Retrieved from "https://public.kitware.com/Wiki/index.php?title=KWScene/Documentation/Supported_Generators/VTK/Image&oldid=21973"