Skip to content


1. Description of the platform/product:

  • name and version of the software: MITK Workbench (not yet released, the TR support features are available in the master of the source code, and will appear in the next stable release)
  • free? yes -
  • commercial? no
  • open source? yes -
  • what DICOM library do you use? DCMTK, GDCM, DCMQI
  • Description of the relevant features of the platform:
  • are multiple tracksets supported in a single file? - No
  • do you support any optional measurement data associated with a track? - No
  • do you support any optional summary statistics associated with a track set? - No
  • do you write any other optional information to the TR file? (e.g. acquisition, model, attribute, algorithm identification etc.)
    • This information is written but it needs to be set manually using the GUI (see screenshot "TagGui.png"). Manually here means by typing typing it into the correponding form in the application GUI.
  • Other notes:
    • the DICOM tags relevant to associate the tractogram to the original image have to be copied manually from the imported DICOM image. Manually here means that to select the image and the new tractogram and to click a button in the application GUI (see screenshot "TagGui.png").
  • Dataset 3 was not read correctly --> no tractogram for dataset 3

2. Read task

TR objects from each platform, loaded and displayed in MITK.

  • Results: tracts 3D visualization
MITK BrainLab 3D Slicer
MITK_dataset_1.dcm TrackSet_DataSet1.dcm 3DSlicer_dataset[..]-v2.dcm
MITK_dataset_2.dcm N/A 3DSlicer_dataset_2[..].dcm
N/A TrackSet_DataSet3.dcm dataset_3_GeSignaHDx.dcm

3. Write tasks

Results of validation using dciodvfy