mitk::Image::Initialize(vtkImageData* vtkimagedata) incorrect for images with origin != (0,0,0)
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	ivo
	Jul 19 2010, 4:30 PM

Description

mitk::Image::Initialize(vtkImageData* vtkimagedata) incorrectly initialized the origin of the mitk::Image for origins != (0,0,0)

To fix this issue add

slicedGeometry->SetOrigin(origin);

after

// re-initialize SlicedGeometry3D

mitkImage.cpp in mitk::Image::Initialize(vtkImageData* ...).

Patch for the issue including a test for it.

mitkImageByVtkImageOriginBugPatch.patch3 KBDownload

Patch for the issue including a test for it.

mitkImageByVtkImageOriginBugPatchWithIncludes.patch4 KBDownload

Same as the obsolete one plus includes/testing macros in test.

mitkImageByVtkImageOriginBugPatchWithIncludes.patch4 KBDownload

[SVN revision 24680]
FIX (#4734): corrected mitk::Image::Initialize(vtkImageData*) for vtkImageData with origin != (0,0,0); added test code for this

	F567: mitkImageByVtkImageOriginBugPatchWithIncludes.patch
	Jul 20 2010, 10:17 AM

	F566: mitkImageByVtkImageOriginBugPatchWithIncludes.patch
	Jul 20 2010, 10:16 AM

	F565: mitkImageByVtkImageOriginBugPatch.patch
	Jul 19 2010, 5:11 PM