Difference between revisions of "2012 Winter Project Week:RTSS"
From NAMIC Wiki
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2011.png|Projects List </gallery> ==Background== Need to add RT support for Slicer. There were some prelimi…') |
|||
| Line 12: | Line 12: | ||
* Queen's University: Andras Lasso | * 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. | ||
| + | </div> | ||
| + | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
| + | <h3>Approach, Plan</h3> | ||
| + | * Specify requirements for representing structure sets in Slicer | ||
| + | * Decide on the design | ||
| + | * Implement the solution in Slicer4 | ||
</div> | </div> | ||
| − | <div style="width: | + | <div style="width: 40%; float: left;"> |
| + | <h3>Progress</h3> | ||
| + | * Preliminary discussions | ||
| + | </div> | ||
| − | + | ==Notes== | |
| − | * | + | *Requirements |
** Support up to 100 structures | ** Support up to 100 structures | ||
| + | ** Support overlapping structures | ||
** Display a name for each structure | ** Display a name for each structure | ||
** Show/hide each structure | ** Show/hide each structure | ||
| Line 27: | Line 38: | ||
** Rigid/deformable transform of the structures | ** Rigid/deformable transform of the structures | ||
** DICOM-RT export | ** DICOM-RT export | ||
| − | * | + | *Design options |
** Store each structure as one labelmap (lots of memory, data loss when converted from contours) | ** 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 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) | ** Store as model or annotation contours (not the usual representation for segmented structures, models cannot be edited) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Delivery Mechanism== | ==Delivery Mechanism== | ||
| − | |||
==References== | ==References== | ||
| Line 53: | Line 50: | ||
* [http://www.dcmtk.org/ DCMTK] | * [http://www.dcmtk.org/ DCMTK] | ||
* [http://plastimatch.org/ Plastimatch] | * [http://plastimatch.org/ Plastimatch] | ||
| − | |||
| − | |||
Revision as of 14:33, 31 December 2011
Home < 2012 Winter Project Week:RTSS
Background
Need to add RT support for Slicer. There were some preliminary work in Slicer3 (using Plastimatch) and new efforts (Plastimatch, DCMTK/DCMRT, SparKit).
Key Investigators
- MGH: Greg Sharp
- NA-MIC: Steve Pieper
- Queen's University: Andras Lasso
Objective
- Find a good representation of RT structure sets in Slicer.
Approach, Plan
- Specify requirements for representing structure sets in Slicer
- Decide on the design
- Implement the solution in Slicer4
Progress
- Preliminary discussions
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)
