Page MenuHomePhabricator
Create Task
Maniphest T19029

VolumeDataVtkMapper is broken and never used
Closed, ResolvedPublic
Actions

Description

The IOExt module which is always loaded with Core, contains the actual volume mapper and replaces the mitkVolumeDataVtkMapper3D.

Also, mitkVolumeDataVtkMapper3D does not work. In the current state, it produces only error messages. It can be repaired but IMO there is no benefit.

Can we delete it?

Event Timeline

• kolbch added projects: MITK, Bugzilla.Apr 24 2015, 6:03 PM
• kolbch added a subscriber: • kolbch.May 19 2015, 11:24 AM

I think it is appropriate to do this before the upcoming release.

nolden added a subscriber: nolden.May 19 2015, 1:16 PM

What was the original purpose of mitkVolumeDataVtkMapper3D?

• kolbch added a comment.May 19 2015, 2:07 PM

It is the default 3d mapper for mitk::Image if there is no other mapper available. it is replaced by mitk::GPUVolumeMapper3D in mitk::IOExtObjectFactory::CreateMapper

The original purpose was to use the vtkVolumeRayCastMapper on images for a CPU volume rendering.

• goch added a subscriber: • goch.May 19 2015, 3:58 PM

I am all in favour of removing a broken class.

• kolbch added a comment.May 20 2015, 2:36 PM

[6274ea]: Merge branch 'bug-19029-DeleteVolumeDataVtkMapper3D'

Merged commits:

2015-05-20 14:25:05 Christoph Kolb [7fdfb5]
delete mapper and references to it

kislinsk edited projects, added MITK (2015-03); removed MITK.Aug 1 2016, 10:49 PM
MITK · MIC · IMSY · DKFZ