Page MenuHomePhabricator
Create Task
Maniphest T15584

Incorrect slice selection with oblique images
Closed, InvalidPublic
Actions

Description

Images with oblique orientation do not allow the user to reach all voxels in the volume (usually in superior-inferior space). Also there is a severe interpolation artefact as the images are "rotated" to a principle orientation (i.e pure axial, etc), which is likely due to expected, but not desirable, interpolation strategy.
I have attached an example screenshot of the nifti. I cannot navigate any lower on the image in question, despite there being many slices below.

I checked, this is not just a DICOM issue. I have uploaded a Nifti version of one of the files that has the problem, and it also will not allow navigation to the inferior slices of the image.

ObliqueIssues.png (443×560 px, 55 KB)

Event Timeline

espak added projects: MITK, Bugzilla.Jul 10 2013, 6:18 PM
espak added a subscriber: espak.

oblique image

01-002_20120131_51657085_004_MGj03C3_oblique_ss_TE00_TI2000.nii.gz506 KBDownload

espak added a comment.Jul 10 2013, 6:21 PM

The problem might be in SliceNavigationController::SelectSliceByPoint( const Point3D &point ).

espak added a comment.Jul 11 2013, 12:07 PM

This condition does not fulfil in the function:

// Check whether the point is somewhere within the slice stack volume;
// otherwise, the default slice (0) will be selected
if ( direction[0] * (point[0] - projectedPoint[0])
   + direction[1] * (point[1] - projectedPoint[1])
   + direction[2] * (point[2] - projectedPoint[2]) >= 0 )
{
  bestSlice = (int)(plane->Distance( point )
    / slicedWorldGeometry->GetSpacing()[2] + 0.5);
}

Also, the distance of the point from the plane of the first slice can be negative. It seems as if the first slice would be in the middle of the image. Is the geometry incorrect?

kislinsk triaged this task as Low priority.Aug 10 2016, 6:26 AM
espak closed this task as Invalid.Oct 26 2016, 9:49 AM

I close this because I found that the geometry I created was wrong.

The MITK display creates the bounding geometry in the original physical space (that is not parallel to the image space) where the corner coordinates are taken from the min and max coordinates of the image corner, and the spacing is the minimum spacing. In this way, you can access any part of the image.

The problem in my case was that I created a geometry that had the same corners as the image, same spacing as the image, but not rotated like the image.

kislinsk changed the task status from Invalid to Spite.Jun 27 2018, 1:33 PM
kislinsk added a project: Bulk Edit.
kislinsk changed the task status from Spite to Invalid.Jun 27 2018, 1:37 PM
kislinsk removed a project: Bulk Edit.
MITK · MIC · IMSY · DKFZ