Page MenuHomePhabricator

MITK - DICOM Seg - loaded DCM SEG not associated with referenced DCM
Open, Unbreak Now!Public

Description

  1. Load DCM
  2. Create new example segmentation
  3. Save dcm seg (Not in the same folder as the original DICOM)
  4. Close Project
  5. Open original DICOM (or dicom seg -> order not relevant)
  6. Open dcm seg

The segmentation is not associated with the original image. (Should be possible, since it is referenced in the metadata)

Version:
Current Release: 18.04.2

OS:
Ubuntu 16.04

Event Timeline

schererj triaged this task as Unbreak Now! priority.Mar 2 2020, 4:19 PM
schererj created this task.
floca added a subscriber: floca.

This task mentions two problems.

  1. loaded segmentation is not associated with the original image
  2. loaded segmentation cannot be stored as DICOM Seg

#2 is a dublicate of T26953: DICOM SEG - Cannot rewrite segmentations as DICOM SEG and should be followed there.

Regarding #1 @schererj what do you need it for? outside (unzipped) scene files it is non trival to persist data manager hirarchy. And in most cases it is also not the most promising way to go.

schererj updated the task description. (Show Details)Mar 2 2020, 5:34 PM

Adapted the task to issue #1 only.

Use case would be the refinement of segmentations.

Is it still a non-trivial thing? I thought we already have the possibility to handle DICOM references? I may miss the point here but when loading a DICOM image with a reference ID or whatever it is called and if this referenced image is present in the current scene, it should be taken into account, right?

floca added a comment.Mar 3 2020, 4:37 PM

Is it still a non-trivial thing? I thought we already have the possibility to handle DICOM references? I may miss the point here but when loading a DICOM image with a reference ID or whatever it is called and if this referenced image is present in the current scene, it should be taken into account, right?

As always: it depends. Depends on where you want to have the relation being refelected. If it is in the data manager view it is non-trival. But (!) I also think that is not the right place to reflect the relation.
This why I posed the question to Jonas above.
Stefan is right that the information is already in the properties and we have with T23808 a PropertyReleationRule that models this dependency.
So the way I would go would be

  • ensure that all properties are correctly set in the segmenation data (e.g. T23774 and T24303...)
  • Implement a DataStorageInspector that displays the relation between segmentation and source images.
  • ignor the old DataManager view ;)
neher added a subscriber: neher.Mar 16 2020, 8:35 AM