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

From KitwarePublic
Jump to navigationJump to search
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Desired Format Support =
= Desired Format Support =


* DICOM
* DICOM (.dcm)
* ANALYZE
* ANALYZE (.hdr/.ima)
* VTI
* XML (.vti)
* MHA
* MetaImage (.mha)
 


= Class Diagrams =
= Class Diagrams =
Line 24: Line 23:
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
Line 40: Line 39:
* Create a KWScene hierarchy that uses vtkDICOMImage, Analyze, XML Readers for 3D images, and vtkImageReader2 (& Factory) for 2D images.
* Create a KWScene hierarchy that uses vtkDICOMImage, Analyze, XML Readers for 3D images, and vtkImageReader2 (& Factory) for 2D images.
* Will have classes
* Will have classes
** ImageNode-KWSGenerator
** FactoryBasedImageNode-KWSGenerator
** DICOMImageNode-KWSGenerator
** DICOMImageNode-KWSGenerator
** AnalyzeImageNode-KWSGenerator
** AnalyzeImageNode-KWSGenerator
** XMLImageNode-KWSGenerator
** XMLImageNode-KWSGenerator
* Classes deriving from kwNodeGenerator will implement a virtual method  
* Classes deriving from kwsImageNodeGenerator will implement a virtual method  
** AlgorithmPointer InstantiateNodeReader()  
** AlgorithmPointer InstantiateNodeReader()  
* Unlike SurfaceNode, ConnectToRenderer does not do anything.  
* Unlike SurfaceNode, ConnectToRenderer does not do anything.  
Line 56: Line 55:
kwsVTKImageNodeGenerator
kwsVTKImageNodeGenerator
kwsVTKGenerator -> kwsVTKNodeGenerator
kwsVTKGenerator -> kwsVTKNodeGenerator
kwsVTKNodeGenerator -> kwsVTKDICOMImageNodeGenerator
kwsVTKNodeGenerator -> kwsVTKImageNodeGenerator
kwsVTKNodeGenerator -> kwsVTKAnalyzeImageNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKFactoryBasedImageNodeGenerator
kwsVTKNodeGenerator -> kwsVTKXMLImageNodeNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKDICOMImageNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKAnalyzeImageNodeGenerator
kwsVTKImageNodeGenerator -> kwsVTKXMLImageNodeNodeGenerator
}
}
</graphviz>
</graphviz>

Latest revision as of 18:55, 22 April 2010

Desired Format Support

  • DICOM (.dcm)
  • ANALYZE (.hdr/.ima)
  • XML (.vti)
  • MetaImage (.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=21991"