Difference between revisions of "Slicer3:DTMRI:GeneralDiffusionFramework"
| Line 17: | Line 17: | ||
= Specifications to encapsulate General Diffusion Data into vtkImageData = | = Specifications to encapsulate General Diffusion Data into vtkImageData = | ||
Slicer 3 intrinsic image data representation is a vtkImageData class. This implies important limitations, namely | Slicer 3 intrinsic image data representation is a vtkImageData class. This implies important limitations, namely | ||
| − | * The | + | * The dimensionality is strictly 3D: the data is supposed to be arranged in a 3D grid and there is not possibilities for further extensions |
| − | * A specific set of point data attributes are allowed: Scalars, Normals, | + | * A specific set of point data attributes are allowed: Scalars, Normals, Vectors and Tensors. |
| + | |||
| + | There is not much we can do about dimensionality. However we can define a convention to be able to store point data attributes beyond the previously commented using new vtkDataArrays in the vtkFieldData. | ||
| + | Then, our work now is to define a clear convention that allow us to make an unequivocal connection between the vtkDataArray an the representation associated to it. | ||
Revision as of 18:09, 27 June 2007
Home < Slicer3:DTMRI:GeneralDiffusionFrameworkDemian Wasserman, Raul San Jose, Lauren O'Donnell
The goal is the define the basic design and data structure specifications to support general diffusion models in the slicer like two tensor diffusion models and higher order spherical harmonics tensors.
Redesign of MRLM
The generalization to general diffusion data models comes through a superclass that generalizes the original behaviour of vtkDiffusionTensorVolumeNode as described in the original design ([1] and [2]) This new class, vtkDiffusionImageVolumeNode, is a child of vtkMRMLTensorVolumeNode and abstract the behaviour related to diffusion imaging. The main members are:
- ID to the Diffusion Weighted Volume Node
- ID to the Baseline Image Volume Node
- ID to the Mask Image Volume Node.
Specifications to encapsulate General Diffusion Data into vtkImageData
Slicer 3 intrinsic image data representation is a vtkImageData class. This implies important limitations, namely
- The dimensionality is strictly 3D: the data is supposed to be arranged in a 3D grid and there is not possibilities for further extensions
- A specific set of point data attributes are allowed: Scalars, Normals, Vectors and Tensors.
There is not much we can do about dimensionality. However we can define a convention to be able to store point data attributes beyond the previously commented using new vtkDataArrays in the vtkFieldData. Then, our work now is to define a clear convention that allow us to make an unequivocal connection between the vtkDataArray an the representation associated to it.
