View Issue Details

IDProjectCategoryView StatusLast Update
0002999Slicer4Core: GUIpublic2017-06-07 23:27
Reporterlassoan Assigned Topieper  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version 
Target VersionSlicer 4.3.0Fixed in VersionSlicer 4.3.0 
Summary0002999: Default slice position is not centered on the slice
Description

By default when loading a volume the slice viewers should show slice positions that intersect the middle of the voxel centers to show the original acquired slices instead of interpolated slices. Currently by default it intersects the edge of the slice.

It also causes seemingly shifted RT structure contours (as if the contours would be shifted by one voxel).

How to reproduce:

Tested with the latest nightly, Windows 64-bit.

TagsNo tags attached.

Relationships

related to 0002878 closedpieper slice locations are at pixel boundaries instead of pixel centers after SnapSliceOffsetToIJK 

Activities

2013-03-11 07:41

 

DefaultSliceOffsetWrong.png (100,464 bytes)
DefaultSliceOffsetWrong.png (100,464 bytes)
pieper

pieper

2013-03-11 08:17

administrator   ~0008108

A similar issue was resolved for the Editor 0002878.

Perhaps we should call SnapSliceOffsetToIJK when propagating the volume selection and centering.

2013-05-09 05:09

 

pieper

pieper

2013-05-09 05:13

administrator   ~0008588

See revision 21976 and close if this has fixed the issue.

The attached screen shot shows the MRhead sample data zoomed in before and after the fix. The slice intersections show that the slices are now centered on the pixels rather than at the boundaries.

lassoan

lassoan

2013-05-11 04:39

developer   ~0008620

Thank you very much. Tested on the latest trunk version on Win64 and it works well now.

Related Changesets

Slicer: 2145-support-for-installing-extension-from-file baac2649

2013-05-09 09:11:39

pieper

Details Diff
BUG: 0002999 Snap to center of pixels when loading volumes

As described in bug report, centering the view to the center
of the pixel makes more sense because it avoids rounding errors
that can occur when there are an even number of pixels and the
slice ends up exactly at the boundary between slices.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21976 3bd1e089-480b-0410-8dfb-8563597acbee
mod - Libs/MRML/Logic/vtkMRMLApplicationLogic.cxx Diff File

Issue History

Date Modified Username Field Change
2013-03-11 07:41 lassoan New Issue
2013-03-11 07:41 lassoan Status new => assigned
2013-03-11 07:41 lassoan Assigned To => kikinis
2013-03-11 07:41 lassoan File Added: DefaultSliceOffsetWrong.png
2013-03-11 08:05 jcfr Assigned To kikinis => pieper
2013-03-11 08:05 jcfr Target Version => Slicer 4.3.0
2013-03-11 08:16 pieper Relationship added related to 0002878
2013-03-11 08:17 pieper Note Added: 0008108
2013-05-09 05:09 pieper File Added: Screen Shot 2013-05-09 at 9.08.22 AM.png
2013-05-09 05:13 pieper Note Added: 0008588
2013-05-09 05:13 pieper Status assigned => resolved
2013-05-09 05:13 pieper Fixed in Version => Slicer 4.3.0
2013-05-09 05:13 pieper Resolution open => fixed
2013-05-11 04:39 lassoan Note Added: 0008620
2013-05-11 04:39 lassoan Status resolved => closed
2017-06-07 23:27 pieper Changeset attached => Slicer 2145-support-for-installing-extension-from-file baac2649