Page MenuHomePhabricator

Expose information of the DICOM reader why blocks where splitted
Open, NormalPublic


Status: Currently the DICOM reader knows internally why a block was splitted (e.g. different tag values, overlapping, gaps in the slice stack). But thin information is not exposed.

Todo: Expose this information in

  1. As IO meta property in the loaded data
  2. As information in the block descriptor -> also printed by the volume analyzis tool

Why: Helpfull for mor robust curation pipelines based on MITK (e.g. for Kaapana or Rocket). E.g. we could then explicitly detect and react on missing slices (= gap in the stack).

Event Timeline

floca triaged this task as Normal priority.Mon, Jun 24, 9:49 AM
floca created this task.
floca added a subscriber: gaoh.