Status: Since the newest software update, dynamic images acquired by the DKFZ MR-PET device, cannot be loaded correctly. Multiple frames of a 3D+t data set have the same time point. It seems like our used tags (acquisition time/date, trigger time) contain not enough information to correctly reconstruct the time geometry of the images generated by the device.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
I found some PET data in XNAT (FS-E Demodata)
Dataset: 3274483764_20171122_PT
When loading both images simultaneously:
Image | real timepoints | MITK 2018.4.0 | Timesteps in 2018 | MITK 2016.11.0 | Timesteps in 2016 |
40012-_Multigate_4Phasen_PRR_AC_Images | 4 | 3 | 0.00 ms, 648.00 ms, 1222.00 ms, 2444.00 ms, 3328 ms | 4 | 0 ms, 1 ms, 2 ms, 3 ms |
40014-_Multigate_4Ampl_PRR_AC_Images | 4 | 3 | 0.00 ms, 648.00 ms, 1222.00 ms, 2444.00 ms, 3328 ms | 4 | 0 ms, 1 ms, 2 ms, 3 ms |
NOTE: MITK 2016.11.0: All 4 timesteps show a different image
NOTE: MITK 2018.4.0: 4Phasen only timesteps 0, 2, 3 show a different image; 4Ampl only timesteps 0, 1, 3 show a different image
Timebounds information is as follows:
40012-_Multigate_4Phasen_PRR_AC_Images min TimeBounds: Step 0: 0 ms Step 1: 1222 ms Step 2: 2444 ms Step 3: 3337 ms max TimeBounds: Step 0: 1222 ms Step 1: 2444 ms Step 2: 3337 ms Step 3: 3337 ms
40014-_Multigate_4Ampl_PRR_AC_Images: min TimeBounds: Step 0: 0 ms Step 1: 648 ms Step 2: 2444 ms Step 3: 3328 ms max TimeBounds: Step 0: 648 ms Step 1: 2444 ms Step 2: 3328 ms Step 3: 3328 ms
When loading each image separately:
Image | real timepoints | MITK 2018.4.0 | Time in 2018 | MITK 2016.11.0 | Time in 2016 |
40012-_Multigate_4Phasen_PRR_AC_Images | 4 | 3 | 0.00 ms, 1222.00 ms, 2440.00 ms, NA | 4 | 0 ms, 1 ms, 2 ms, 3 ms |
40014-_Multigate_4Ampl_PRR_AC_Images | 4 | 3 | 0.00 ms, 648.00 ms, 2444.00 ms, NA | 4 | 0 ms, 1 ms, 2 ms, 3 ms |
Last timestep in each image can not be accessed (comp. T24766).
Comment Actions
Talked with the colleagues. Currently the problem can not be reproduced (maybe another update fixed the problem). So "watchfull waiting". We will reopen/reprioritze it, if it occurs again.