Master's Thesis - Studierstube Augmented Reality Project - Graz ...

5.2 iMEDgine extensions
Figure 5.2: A dataset for flow data and its interfaces and inheritances as simplified
UML class diagram. For the sake of clarity, all methods are cut in this representation.
The full diagram can be found in figure B.1.
as presented in tables A.1 to A.9 in chapter 4 will be traversed with this class. Unfortunately,
the flow data and related images are organized in temporal order instead
of a required volumetric order. Thus a reorganization before storing them in a dataset
class is unavoidable and may take some time. The DICOM image processing is done
with the help of given paths to the images in the *.4dd files 1 . For each volume image
stack a new iMEDgine DICOM volume image dataset will be read by its own DICOM
volume I/O and made available by the flow field volume dataset in a dataset vectorbased
structure. Note that this effort only applies for anatomical (rephased) volumetric
image stacks; the flow data itself is, as already described, preprocessed and numerically
stored in *.4dd files. The reorganization to a volumetric order can be already done
by the read strings containing the paths to the images. Since each temporal volume
consists of exactly the same number of slice images in the same order, this task can be
solved accordingly. The first image paths in the image file section (table A.4 ) of each
*.4dd file refers always to the first volume and so on. The DICOM volume I/O itself
utilizes the Insight Segmentation and Registration Toolkit’s [ITK2006] GDCM library
1 If the data cease to exist at the given lo6cation, an alternative path but containing the same data
will be asked for.
84