Summary of problem description

actual behaviour

When MITK writes images via ITK, it uses the templated class itkImageFileWriter, which is multiplexed over pixel type and dimension in mitkImageWriter. This is actually not necessary, but prevents the writing of vector images via this way.

expected behaviour

itkImageIO, which actually writes the data, can directly be initialized on MITK side, especially with dimension and pixel type. This makes the multiplexing unnecessary.

Cause of the bug

Not really a bug, it works both ways. But, vector images can not be included in the multiplexing, because many algorithms can't handle them and would not compile. So, for each possible vector image, a seperate function is declared in the moment. This is all unnecessary, bacause all information for writing the image is present on MITK side.

Proposed solution

Feed itkImageIO with all information it needs directly in mitkImageWriter.

Affected classes

mitkImageWriter mitkItkImageWrite

mitkImageWriterTest

How will the bugfix get tested?

Unit test will be adapted in mitkImageWriterTest