these dwi files use a different tag for sorting their files (fixed)
and also use a different way to save their slice locations (in progress)
Description
Description
Related Objects
Related Objects
- Mentioned In
- T27033: Clean up stale remote branches
Event Timeline
Comment Actions
Problem seems to be related to the different way of representing single slices:
(0020,9057) describes the Slice-Index wihtin stack,
which seems to be ignored in construction of Diffusion images,
loading these images as regular dicom files works (w.r.t. to slice spacing)
next this function needs to be checked for the part that recognizes different
slices:
void mitk::GEDicomDiffusionImageHeaderReader::Update()
Comment Actions
within mitk::GEDicomDiffusionImageHeaderReader::Update()
no location is set, only slice thickness, spacing is set,
since each slice is handled seperately no different positions for them are stored.