Difference between revisions of "2016 Summer Project Week/MeVisLab SEG Colors"
From NAMIC Wiki
Hans.meine (talk | contribs) (update progress with implementation plan) |
Hans.meine (talk | contribs) (add steve and christian) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 7: | Line 7: | ||
* Hans Meine | * Hans Meine | ||
* Andrey Fedorov | * 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> | ||
Line 34: | Line 41: | ||
** 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?). | ** 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. | ** GUI shared as well, but with readonly fields for the display. | ||
− | ** Many tags | + | ** 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. | ** 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 ColorsKey Investigators
- Hans Meine
- Andrey Fedorov
- Christian Herz
- Steve Pieper
Project Description
Objective
- Make it possible to assign SEG
colorsproperties in MeVisLab. - Make it possible to read / use existing SEG
colorsproperties 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.