Page MenuHomePhabricator

Missing FileWriters and FileReaders
Closed, WontfixPublic

Description

Currently, MITK contains the following data classes:

  1. mitk::BaseData
    • mitk::BaseDataImplementation
    • mitk::ColoredRectangleRendering
    • mitk::Contour
    • mitk::ContourSet
    • mitk::DiffusionVolumes< TPixelType >
    • mitk::GeometryData o mitk::Geometry2DData
    • mitk::GradientBackground
    • mitk::ItkBaseDataAdapter
    • mitk::LogoRendering
    • mitk::PointData
    • mitk::PointSet o mitk::Mesh
    • mitk::SlicedData o mitk::Image + mitk::QBallImage + mitk::SeedsImage + mitk::TensorImage
    • mitk::Surface o mitk::BoundingObject + mitk::BoundingObjectGroup + mitk::Cone + mitk::Cuboid + mitk::Cylinder + mitk::Ellipsoid + mitk::ExtrudedContour + mitk::Plane o mitk::TrackingVolume
    • mitk::UnstructuredGrid
    • mitk::VtkWidgetRendering

In contrast, it contains only the following FileWriter and FileReader classes:

  1. mitk::FileReader
    • mitk::FileSeriesReader o mitk::DataTreeNodeFactory o mitk::PicVolumeTimeSeriesReader o mitk::StlVolumeTimeSeriesReader o mitk::VtkVolumeTimeSeriesReader
    • mitk::ItkImageFileReader
    • mitk::NrrdDiffusionVolumesReader< TPixelType >
    • mitk::NrrdQBallImageReader
    • mitk::NrrdTensorImageReader
    • mitk::ParRecFileReader
    • mitk::PicFileReader
    • mitk::PointSetReader
    • mitk::RawImageFileReader
    • mitk::VtiFileReader
    • mitk::VtkImageReader
  1. mitk::FileWriter
    • mitk::FileWriterWithInformation o mitk::NrrdDiffusionVolumesWriter< TPixelType > o mitk::NrrdQBallImageWriter o mitk::NrrdTensorImageWriter
    • mitk::ImageWriter
    • mitk::PicFileWriter
    • mitk::PointSetWriter
    • mitk::SurfaceVtkWriter< VTKWRITER >
    • mitk::UnstructuredGridVtkWriter< VTKWRITER >

--> Many data objects can not be saved to a file, many can not be read from a file.

Which ones are needed? Who implements them?
If there is no Reader/Writer, they also can not be saved in a scene file with SceneSerialization.

Event Timeline

Serialization of objects of Geometry3D and sub-classes would allow to store various Geometry information contained in a scene. If a mechanism for saving/loading Geometry objects was available in MITK, it would also be straightforward to impelemtn a writer for mitk::GeometryData (e.g., needed to store curved geometries/planes)

Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.

kislinsk claimed this task.
kislinsk added a subscriber: kislinsk.
This task was automatically closed because it wasn't updated at least since July 2016 (over 2 years). Please re-open this task if you think that it is still relevant. This most probably means that you will resolve it.