2012 Winter Project Week:RTTools - Revision history

Gregsharp: /* Detailed plan */

2012-01-13T00:57:39Z

Detailed plan

2012-01-13T00:55:42Z

Detailed plan

2012-01-13T00:55:21Z

Detailed plan

2012-01-13T00:23:27Z

2012-01-12T23:34:27Z

2012-01-12T23:23:10Z

2012-01-12T23:18:38Z

Key Investigators

2012-01-12T23:09:34Z

2012-01-10T15:32:17Z

2012-01-09T22:32:17Z

@@ Line 69: / Line 69: @@
 *** Module input: UID, reference to the DICOM database, name of data to be loaded
 *** Module output: MRML nodes imported into the scene
 * Validation:
 ** Assemble data sets from different vendors

@@ Line 69: / Line 69: @@
 *** Module input: UID, reference to the DICOM database, name of data to be loaded
 *** Module output: MRML nodes imported into the scene
-** Validation:
+* Validation:
-*** Assemble data sets from different vendors
+** Assemble data sets from different vendors
 ==Delivery Mechanism==

@@ Line 69: / Line 69: @@
 *** Module input: UID, reference to the DICOM database, name of data to be loaded
 *** Module output: MRML nodes imported into the scene
 ==Delivery Mechanism==

@@ Line 73: / Line 73: @@
 This work will be delivered to the NA-MIC Kit as a <b>Slicer loadable module</b>.
-The source code is available in the [https://subversion.assembla.com/svn/sparkit/ SparKit repository]
+The source code is available in the following locations:
 ==References==

@@ Line 42: / Line 42: @@
 * Sample data collected
 * DCMRT build in Slicer OK
 * Retrieval of RT tags into DICOM module database (see [http://www.na-mic.org/Wiki/index.php/File:Screenshot_Before_After_DICOMModule_KGH_Prostate.png screenshot])
 * New hidden DicomRtImport loadable module that is called when importing any DICOM object. It tryes to load it first as RT then passes to the Volumes module's loader
 ** Improvement needed: DICOMIOFactory - a DICOM importer module has to register into this, and when loading a DICOM file, it decides which one to call
 * Create ribbon models from the found RT Structure Sets and add them in the Slicer Scene as new MRML nodes. The name and color is also set (see [http://www.na-mic.org/Wiki/index.php/File:Screenshot_DicomRtImport_3D_KGH_Prostate_wSlice.png screenshot])
 </div>

@@ Line 2: / Line 2: @@
 <gallery>
 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<br>(Summer 2011 result)
 </gallery>

← Older revision		Revision as of 22:32, 9 January 2012
Line 45:		Line 45:

	<div style="width: 97%; float: left;">		<div style="width: 97%; float: left;">
		+
		+	==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==		==Delivery Mechanism==