Page MenuHomePhabricator

Depends on #11948: Crosshair position is wrong in axial view after reinit on other image
Closed, WontfixPublic

Assigned To
Authored By
Sep 25 2013, 2:21 PM
Referenced Files
F1054: snapshot3.png
Oct 16 2013, 3:38 PM
F1053: snapshot2.png
Oct 16 2013, 3:37 PM
F1052: snapshot1.png
Oct 16 2013, 3:36 PM
F1051: crosshairBug_afterReinit.png
Sep 25 2013, 2:22 PM
F1050: crosshairBug.png
Sep 25 2013, 2:22 PM


If the scene was reinited on another image the crosshair position in the axial view might be wrong.

To reproduce this bug load these two images from the MITK-data repsoitory (MITK-superbuild\CMakeExternals\Source\MITK-Data):

  • mini3D.pic.gz (subfolder RenderingTestData)
  • Pic3D.nrrd

Then make the Pic3D image invisible in the data manager and click "reinit" on this image.

Afterwards zoom to the mini3D image, which should be still visible and select a pixel from the upper row in the sagital view. The axial view won't show a pixel which is clearly a bug.

If you click "reinit" on the mini3D image afterwards, everything works like expected.

I'll attach two screenshots which show this bug.

Event Timeline

franza added a subscriber: franza.

Screenshot showing the bug.

crosshairBug.png (1×1 px, 146 KB)

Screenshot showing the correct behaviour after reinit.

crosshairBug_afterReinit.png (1×1 px, 133 KB)

Works for me on Linux, however, I'm not on the current master.

My current MITK branch is:

Merge branch 'bug-15741-NewPickingOption' by Sven Mersmann.

I will double-check this with the current release.

Changing severity. Critical is only a bug which leads to a loss of data, e.g. like a programm crash.

We should try to reproduce this on the current master. Can be done by anyone! Important!

The bug is still present in current master (4930d6a146d699edd81fa36ff0e36084d6d49823).

We took the steps described in the first comment.

Some additional information:

When a pixel in the upper row in sagittal view is selected the statusbar displays "No image information at this position!" (see screenshot "Statusbar no pixel value"). When a pixel below the bottom row of the image in the sagittal view is selected, the statusbar shows a pixel value (see screenshot "Statusbar pixel value").

Additionally an offset between the planes can be seen in the 3d view (see screnshot "Offset of planes in 3d view"). When scrolling through slices the plane disappears in 3d view, before it reached the last possible position.

The planes are displayed wrongly in all views. There is one row of pixels in every plane that looks like being interpolated (same values as next row).

Current release is finished. Reseting target milestone...

Adrian left the group, reset to default

kislinsk claimed this task.
kislinsk added a project: Auto-closed.
kislinsk added a subscriber: kislinsk.

Hi there! 🙂

This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑

Best wishes,
The MITK devs

kislinsk removed kislinsk as the assignee of this task.May 26 2020, 12:05 PM
kislinsk removed a subscriber: kislinsk.