Difference between revisions of "2012 Winter Project Week:RTSS"

From NAMIC Wiki
Jump to: navigation, search
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2011.png|Projects List </gallery> ==Background== Need to add RT support for Slicer. There were some prelimi…')
 
 
(9 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
<gallery>
 
<gallery>
 
Image:PW-SLC2011.png|[[2012_Winter_Project_Week#Projects|Projects List]]
 
Image:PW-SLC2011.png|[[2012_Winter_Project_Week#Projects|Projects List]]
 +
Image:2012-01-12-editor-sketch.png|Sketch of editor design
 
</gallery>
 
</gallery>
  
==Background==
+
==Key Investigators==
Need to add RT support for Slicer. There were some preliminary work in Slicer3 (using Plastimatch) and new efforts (Plastimatch, DCMTK/DCMRT, SparKit).
+
 
 +
Greg Sharp, Steve Pieper, Andras Lasso, Kevin Wang, Csaba Pinter
  
==Key Investigators==
+
<div style="margin: 20px;">
* MGH: Greg Sharp
 
* NA-MIC: Steve Pieper
 
* Queen's University: Andras Lasso
 
  
 +
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Objective</h3>
 
<h3>Objective</h3>
* Find a good representation of RT structure sets in Slicer.
+
Find a good representation of RT structure sets in Slicer. There were some preliminary work in Slicer3 (using Plastimatch) and new efforts (Plastimatch, DCMTK/DCMRT, SparKit).
 
 
 
</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>
* Specify requirements for representing structure sets in Slicer:
+
* Specify requirements for representing structure sets in Slicer
** Support up to 100 structures
+
* Decide on the design
** Display a name for each structure
 
** Show/hide each structure
 
** Manual editing of each structure
 
** Rigid/deformable transform of the structures
 
** DICOM-RT export
 
* Decide on the design. Options:
 
** Store each structure as one labelmap (lots of memory, data loss when converted from contours)
 
** Store multiple structure in a labelmap as bitfield (limited to 32 structures, complicated editing, data loss when converted from contours)
 
** Store as model or annotation contours (not the usual representation for segmented structures, models cannot be edited)
 
 
* Implement the solution in Slicer4
 
* Implement the solution in Slicer4
 
 
</div>
 
</div>
  
 
<div style="width: 40%; float: left;">
 
<div style="width: 40%; float: left;">
 
 
<h3>Progress</h3>
 
<h3>Progress</h3>
* Preliminary discussions
+
* Preliminary discussions, requirement specification, identification of design options completed.
 +
* Mockup of UI available for feedback
 +
</div>
  
</div>
 
 
</div>
 
</div>
  
 
<div style="width: 97%; float: left;">
 
<div style="width: 97%; float: left;">
  
==Delivery Mechanism==
+
==Notes==
 
+
*Requirements
 +
** Support up to 100 structures
 +
** Support overlapping structures
 +
** Display a name for each structure
 +
** Show/hide each structure
 +
** Manual editing of each structure
 +
** Rigid/deformable transform of the structures
 +
** DICOM-RT export
 +
*Design options
 +
** Store each structure as one labelmap (lots of memory, data loss when converted from contours)
 +
** Store multiple structure in a labelmap as bitfield (limited to 32 structures, complicated editing, data loss when converted from contours)
 +
** Store as model or annotation contours (not the usual representation for segmented structures, models cannot be edited)
 +
* Considerations
 +
** Structure contours must be associated with background volume DICOM data in order to be exported correctly.  This effort should be coordinated with the [[2012_Project_Week:QIN-SAM|DICOM SR/AIM annotation effort]]
 +
** How should these be represented in ITK and the SEM?
  
 
==References==
 
==References==
 
 
* [https://www.assembla.com/spaces/sparkit/wiki SparKit project wiki]
 
* [https://www.assembla.com/spaces/sparkit/wiki SparKit project wiki]
 
* [http://www.dcmtk.org/ DCMTK]
 
* [http://www.dcmtk.org/ DCMTK]

Latest revision as of 00:53, 13 January 2012

Home < 2012 Winter Project Week:RTSS

Key Investigators

Greg Sharp, Steve Pieper, Andras Lasso, Kevin Wang, Csaba Pinter

Objective

Find a good representation of RT structure sets in Slicer. There were some preliminary work in Slicer3 (using Plastimatch) and new efforts (Plastimatch, DCMTK/DCMRT, SparKit).

Approach, Plan

  • Specify requirements for representing structure sets in Slicer
  • Decide on the design
  • Implement the solution in Slicer4

Progress

  • Preliminary discussions, requirement specification, identification of design options completed.
  • Mockup of UI available for feedback

Notes

  • Requirements
    • Support up to 100 structures
    • Support overlapping structures
    • Display a name for each structure
    • Show/hide each structure
    • Manual editing of each structure
    • Rigid/deformable transform of the structures
    • DICOM-RT export
  • Design options
    • Store each structure as one labelmap (lots of memory, data loss when converted from contours)
    • Store multiple structure in a labelmap as bitfield (limited to 32 structures, complicated editing, data loss when converted from contours)
    • Store as model or annotation contours (not the usual representation for segmented structures, models cannot be edited)
  • Considerations
    • Structure contours must be associated with background volume DICOM data in order to be exported correctly. This effort should be coordinated with the DICOM SR/AIM annotation effort
    • How should these be represented in ITK and the SEM?

References