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

From NAMIC Wiki
Jump to: navigation, search
(Initial project description)
 
(add steve and christian)
 
(4 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
==Key Investigators==
 
==Key Investigators==
 
* Hans Meine
 
* Hans Meine
* Andrey Fedorov (Consultant ;-) )
+
* Andrey Fedorov
 +
* Christian Herz
 +
* Steve Pieper
  
 
==Project Description==
 
==Project Description==
Line 12: Line 14:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Objective</h3>
 
<h3>Objective</h3>
* Make it possible to assign SEG colors in MeVisLab.
+
* Make it possible to assign SEG <strike>colors</strike> properties in MeVisLab.
* Make it possible to read / use existing SEG colors in MeVisLab.
+
* Make it possible to read / use existing SEG <strike>colors</strike> properties in MeVisLab.
 
</div>
 
</div>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Approach, Plan</h3>
 
<h3>Approach, Plan</h3>
 +
* Learn about what's necessary to do that.
 +
** DICOM structures
 +
** MeVisLab's DICOM tree representation
 +
** DirectDicomImport's behavior w.r.t. SEG files
 +
** existing infrastructure for reading / modifying DICOM tags
 
* Implement modules for accessing / modifying the DICOM tree for the two objectives.
 
* Implement modules for accessing / modifying the DICOM tree for the two objectives.
 
</div>
 
</div>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Progress</h3>
 
<h3>Progress</h3>
*  
+
* 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 [http://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_A.51.3.html which data is necessary and interesting], and where it is stored:
 +
** ClinicalTrial{SeriesID,TimePointID,CoordinatingCenterName}
 +
** [http://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.8.20.2.html SegmentationType, SegmentationFractionalType] (binary / fractional probability / fractional occupancy)
 +
** [http://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.8.20.4.html#table_C.8.20-4  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.
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 09:49, 25 June 2016

Home < 2016 Summer Project Week < MeVisLab SEG Colors

Key Investigators

  • Hans Meine
  • Andrey Fedorov
  • Christian Herz
  • Steve Pieper

Project Description

Objective

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

Approach, Plan

  • Learn about what's necessary to do that.
    • DICOM structures
    • MeVisLab's DICOM tree representation
    • DirectDicomImport's behavior w.r.t. SEG files
    • existing infrastructure for reading / modifying DICOM tags
  • 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.