Difference between revisions of "2016 Summer Project Week/MeVisLab SEG Colors"

From NAMIC Wiki
Jump to: navigation, search
(document progress)
(update progress with implementation plan)
Line 31: Line 31:
 
*** SegmentedPropertyCategoryCode, SegmentedPropertyTypeCode, SegmentedPropertyTypeModifierCode sequences
 
*** SegmentedPropertyCategoryCode, SegmentedPropertyTypeCode, SegmentedPropertyTypeModifierCode sequences
 
*** tracking ID / UIDs
 
*** tracking ID / UIDs
 +
* Implementation Plan:
 +
** Probably two separate modules for just displaying / editing, but sharing a lot of code (base class? Classes implementing reading / writing of fields of certain DICOM macros?).
 +
** GUI shared as well, but with readonly fields for the display.
 +
** Many tags *could* be added via DicomTagModify, but C++ module needed for SegmentSequence -> everything should be in C++ then.
 +
** Module with multiple inputs could be used for creating multi-segment SEG files.
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 07:15, 25 June 2016

Home < 2016 Summer Project Week < MeVisLab SEG Colors

Key Investigators

  • Hans Meine
  • Andrey Fedorov

Project Description

Objective

  • Make it possible to assign SEG colors in MeVisLab.
  • Make it possible to read / use existing SEG colors in MeVisLab.

Approach, Plan

  • Implement modules for accessing / modifying the DICOM tree for the two objectives.

Progress

  • A new DICOM tree browser has been implemented. (The existing one had strange problems with showing all SegmentSequence subtags.)
  • The DICOM import configuration (DirectDicomImport module) has been extended to properly import multi-segment files.
  • It has been identified which data is necessary and interesting, and where it is stored:
    • ClinicalTrial{SeriesID,TimePointID,CoordinatingCenterName}
    • SegmentationType, SegmentationFractionalType (binary / fractional probability / fractional occupancy)
    • per-segment information
      • LabelID, SegmentDescription, color
      • algorithm type (automatic, semiautomatic, manual)
      • SegmentedPropertyCategoryCode, SegmentedPropertyTypeCode, SegmentedPropertyTypeModifierCode sequences
      • tracking ID / UIDs
  • Implementation Plan:
    • Probably two separate modules for just displaying / editing, but sharing a lot of code (base class? Classes implementing reading / writing of fields of certain DICOM macros?).
    • GUI shared as well, but with readonly fields for the display.
    • Many tags *could* be added via DicomTagModify, but C++ module needed for SegmentSequence -> everything should be in C++ then.
    • Module with multiple inputs could be used for creating multi-segment SEG files.