screenshot of the two images that should be congruent

The problem here is that the world geometry which is used to resample the data objects in order to draw their textures onto the render window planes is composed of the different geometries of the data objects. Hence the world geometry which is used for sampling the data to be displayed often doesn't match with the data objects geometries and therefor rendering errors occur.

The solution is not trivial and should be discussed in the next meeting.

Added keyword RFD

This bug has a high severity and was not fixed within the 2013-06 release. Setting target milestone to next release.

This bug is now part of the Bugsquashing SCRUM program.

Andreas already described the problem above. The affected class is mitk::ExtractSliceFilter which is used to extract the rendered images. This is done in mitk::ImageVtkMapper2D and hence is a rendering bug, not a geometry bug.

mitk::ImageVtkMapper2D checks for a mitk::BoolProperty named "in plane resample extent by geometry". If this property is set to true, the problem disappears.

Added Markus Engel to Cc since he write the line that checks for "in plane resample extent by geometry".

if the property "in plane resample extent by geometry" is false, the image geometry is used. If the property is true, spacing of the output 2S image depends on the currently selected world geometry and *not* on the image itself.

Current release is finished. Reseting target milestone...