I'm using Stefans MITK-2018.4.0-linux64 Installer (sorry for being to exclusive) on ubuntu 16.04. Stefan will be able to give you more information about the current status of this version and he will also be able to decide whether a bug fix is necessary at all.
In the past I used to work with raw images in nifti format and the corresponding segmentations in nifit format.
Now however I used a raw image in DICOM format and the corresponding segmentation in nifti format. When I drag an drop the DICOM and the nifti into MITK's data manager two difference things happened (at this moment I am not able to predict whether case 1 or case 2 will occur):
- "time line" will be concatenated, meaning: both DICOM and nifit have 30 time steps, after loading both of them into MITK both will have 60, although only 30 of them contain unique content -> by sliding through time the file loaded first will change for the first 30 time steps, then the image will freeze for the last 30 time steps before it starts again to move. the file loaded last will change its content for the last 30 time steps.
- The file which was loaded last (either DICOM or nifti) will behave as expected: by sliding through all 30 time steps the image will change 30 time. The file which was loaded first however will change its content over the 30 time steps (30 time steps are shown in the "image navigator") only one or two times.
in my case (hope it is not an issue of the data I use)
- load an arbitrary 3d+t DICOM image and the corresponding segmentation (nifti)
- slide through time -> strange behavior should occur
Thanks you MITK!