Difference between revisions of "2016 Summer Project Week/Segmentation Editor and Terminology"
From NAMIC Wiki
| Line 20: | Line 20: | ||
* The initial plan was for the Segment Editor to incoporate the display of terminology, ported from the Editor module. The next stage is to add support for editing the terminologies and adding new ones. | * The initial plan was for the Segment Editor to incoporate the display of terminology, ported from the Editor module. The next stage is to add support for editing the terminologies and adding new ones. | ||
* Review overview sildes [https://www.slicer.org/slicerWiki/index.php/File:20160526_Segmentations.pptx | Segmentations] | * Review overview sildes [https://www.slicer.org/slicerWiki/index.php/File:20160526_Segmentations.pptx | Segmentations] | ||
| − | * Source code review: [https://subversion.assembla.com/svn/slicerrt/trunk/SlicerRt/src/ | SlicerRT], with a focus on containers (vtkSegment, vtkSegmentation, vtkMRMLSegmentationNode), and widget GUI (Segmentations | + | * Source code review: [https://subversion.assembla.com/svn/slicerrt/trunk/SlicerRt/src/ | SlicerRT], with a focus on containers (vtkSegment, vtkSegmentation, vtkMRMLSegmentationNode), and widget GUI (Segmentations Widgets qMRMLSegmentsTableView) |
* Compare to web app for populating SEG metadata: http://qiicr.org/dcmq | * Compare to web app for populating SEG metadata: http://qiicr.org/dcmq | ||
</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> | ||
| − | + | * Tue Jun 21: Csaba and Nicole met and discussed ways to incorporate the terminology information into the segment editor | |
| + | ** Each segmentation node has a custom temporary color table that's built up from color selected for each segment. | ||
| + | *** Add a node reference to the segmentation node pointing to the color node that is used to build the custom color table (generic anatomy colors has terminology associated with it). This will help on load as the segment has the color index and the custom color table will be rebuilt from the reference color node. | ||
| + | *** When creating the new temp color node, also create a new terminology associated with it | ||
| + | ** Adding a new segment | ||
| + | *** A color RGB is set on the display node, that's used to rebuild the custom color table on load | ||
| + | *** Consolidate to the segment editor | ||
| + | *** Bring up the CTK color picker by default | ||
| + | *** Extend/fix the CTK color picker: | ||
| + | **** Bring up the custom color node by default | ||
| + | **** How to best show if adding a new color or editing an old one? | ||
| + | **** Fix the bug where you can pick a new color for a segment, but if you click on a different color in the color picker's table it still sets the color for the entry that was clicked in the editor GUI (disable selection highlight?) | ||
| + | **** Add display of the terminology associated with the color node displayed | ||
| + | **** Add terminology editing/look up to set a new terminology | ||
| + | **** Consider loading a segmentation node from disk and rebuilding the new terminology - will each segment need to have a the terminoology category, property, region and modifiers set? | ||
| + | ** Add tool tips showing terminology, as in Colors module | ||
</div> | </div> | ||
</div> | </div> | ||
Revision as of 11:42, 21 June 2016
Home < 2016 Summer Project Week < Segmentation Editor and Terminology
Slicer 4.5 Editor with terminology
Key Investigators
- Nicole Aucoin (BWH)
- Csaba Pinter (Queens)
- Andrey Fedorov (BWH)
Project Description
Objective
- Build on the work done in the Segmentations Integration project to incoporate terminology information from Reporting module as ported to the Editor module as documented in issue 4047 and committed as svn 24742.
Approach, Plan
- The initial plan was for the Segment Editor to incoporate the display of terminology, ported from the Editor module. The next stage is to add support for editing the terminologies and adding new ones.
- Review overview sildes | Segmentations
- Source code review: | SlicerRT, with a focus on containers (vtkSegment, vtkSegmentation, vtkMRMLSegmentationNode), and widget GUI (Segmentations Widgets qMRMLSegmentsTableView)
- Compare to web app for populating SEG metadata: http://qiicr.org/dcmq
Progress
- Tue Jun 21: Csaba and Nicole met and discussed ways to incorporate the terminology information into the segment editor
- Each segmentation node has a custom temporary color table that's built up from color selected for each segment.
- Add a node reference to the segmentation node pointing to the color node that is used to build the custom color table (generic anatomy colors has terminology associated with it). This will help on load as the segment has the color index and the custom color table will be rebuilt from the reference color node.
- When creating the new temp color node, also create a new terminology associated with it
- Adding a new segment
- A color RGB is set on the display node, that's used to rebuild the custom color table on load
- Consolidate to the segment editor
- Bring up the CTK color picker by default
- Extend/fix the CTK color picker:
- Bring up the custom color node by default
- How to best show if adding a new color or editing an old one?
- Fix the bug where you can pick a new color for a segment, but if you click on a different color in the color picker's table it still sets the color for the entry that was clicked in the editor GUI (disable selection highlight?)
- Add display of the terminology associated with the color node displayed
- Add terminology editing/look up to set a new terminology
- Consider loading a segmentation node from disk and rebuilding the new terminology - will each segment need to have a the terminoology category, property, region and modifiers set?
- Add tool tips showing terminology, as in Colors module
- Each segmentation node has a custom temporary color table that's built up from color selected for each segment.
