Difference between revisions of "2012 Winter Project Week:RTTools"
From NAMIC Wiki
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
<gallery> | <gallery> | ||
| − | Image:PW- | + | Image:PW-SLC2012.png|[[2012_Winter_Project_Week#Projects|Projects List]] |
Image:DVH_in_Slicer.png|[[DVH chart in Slicer4]] | Image:DVH_in_Slicer.png|[[DVH chart in Slicer4]] | ||
</gallery> | </gallery> | ||
Revision as of 15:32, 10 January 2012
Home < 2012 Winter Project Week:RTTools
Background
We propose to extend 3D Slicer to support RT research under the Software Platform and Adaptive Radiotherapy Kit (SparKit) project. OCAIRO investigators we have identified some of the key features required from a 3D Slicer based RT research platform. This project week we are going to finish integrating our first new feature to Slicer4 - the import of DICOM RT datasets.
Key Investigators
- Queen's University: Csaba Pinter, Andras Lasso
- Toronto UHN: Kevin Wang
- MGH: Greg Sharp
Objective
- Add DICOM-RT import functionality to Slicer4
- Outline the data format in which the structure set is stored
- Test it on the most real-life datasets possible
Approach, Plan
- Utilize new DCMTK (that contains DCMRT) in CTK
- Convert internal DCMRT structures to MRML nodes (models, labelmaps, etc.)
- Apply necessary GUI changes that are needed for RT import in CTK
Progress
- Slicer4 build OK
- Sample data collected
- DCMRT build in Slicer OK
Detailed plan
- Create an extension module: DicomRtImport (Csaba)
- Call a method of the DicomRtImport module when the user requests DICOM object loading. Method's input: UID. If the method finds a structure set then it adds it to the scene. (Csaba)
- Create a VTK filter that can read structure set from a DICOM-RT structure set and has a vtkPolyData output (Kevin)
- Integrate the VTK filter into the DicomRtImport module (Kevin)
- Add the vtkPolyData to the scene as a MRML model node (Kevin/Csaba)
- Discuss DicomPlugin interface with Steve:
- The module should not be visible for the user in the usual module list (it should show up somehow in the DICOM module)
- Data discovery:
- Module input: UID, reference to the DICOM database
- Module output: list of data it can read from the object
- Data import:
- Module input: UID, reference to the DICOM database, name of data to be loaded
- Module output: MRML nodes imported into the scene
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a Slicer loadable module. The source code is available in the SparKit repository
