2012 Winter Project Week DICOM RT Breakout - Revision history

Pinter: /* Plan */

2012-01-12T23:31:52Z

Plan

Pinter: /* Plan */

2012-01-12T23:30:59Z

Plan

Lasso at 23:30, 12 January 2012

2012-01-12T23:30:31Z

Pinter: /* Plan */

2012-01-11T21:30:22Z

Plan

Pinter: /* Agenda */

2012-01-11T02:03:46Z

Agenda

Pinter: /* Design questions */

2012-01-11T02:02:35Z

Design questions

Pinter: /* Plan */

2012-01-11T01:16:07Z

Plan

Pinter at 01:14, 11 January 2012

2012-01-11T01:14:34Z

Fedorov: /* Agenda */

2012-01-10T22:22:53Z

Agenda

Pinter: /* Organizational Topics */

2012-01-10T22:17:54Z

Organizational Topics

@@ Line 40: / Line 40: @@
 == Plan ==
 * Telecons
-** Internal (just us), next week (Jan 16-20) - to be organized by the SparKit group<br>Participants:
+** Internal (just us), next week (Jan 16-20) - to be organized by the SparKit group<br>Participants please sign up on the bottom of the page
 ** DCMTK
 *** What can go reasonably in DCMTK should go there as lowest level toolkit

@@ Line 40: / Line 40: @@
 == Plan ==
 * Telecons
-** Internal (just us), next week (Jan 16-20) - to be organized by the SparKit group
+** Internal (just us), next week (Jan 16-20) - to be organized by the SparKit group<br>Participants:
 ** DCMTK
 *** What can go reasonably in DCMTK should go there as lowest level toolkit

← Older revision		Revision as of 23:30, 12 January 2012
Line 66:		Line 66:
	*** The file can be kept in memory		*** The file can be kept in memory
	*** Pointer in the vtkMRMLNode to a DCMTK object		*** Pointer in the vtkMRMLNode to a DCMTK object
		+
		+	== Follow-up meeting ==
		+	'''Sign up here to get invitation to the meeting with CTK and DCMTK developer groups'''
		+	*Andras Lasso
		+	*Csaba Pinter
		+	*Kevin Wang
		+	*Steve Pieper
		+	*Greg Sharp

@@ Line 39: / Line 39: @@
 == Plan ==
-* Telecon with DCMTK group, CTK group
+* Telecons
-** DCMTK - next week (Jan 14-) - to be organized by the SparKit group
+** Internal (just us), next week (Jan 16-20) - to be organized by the SparKit group
 *** What can go reasonably in DCMTK should go there as lowest level toolkit
 *** Middle level addition for interpreting raw data

@@ Line 12: / Line 12: @@
 =Agenda=
 *3:10-3:20, Welcome, Goal of the meeting, Agenda, Taking notes in wiki
-*3:20-3:35, Introduction of [https://www.assembla.com/spaces/sparkit/wiki/SlicerRt SlicerRT] project (under [http://www.assembla.com/spaces/sparkit SparKit]) goals, design options - Csaba Pinter
+*3:20-3:35, Introduction of [https://www.assembla.com/spaces/sparkit/wiki/SlicerRt SlicerRT] project (under [http://www.assembla.com/spaces/sparkit SparKit]) goals, design options - Csaba Pinter ([[media:DICOMRTImportInSlicer4.pptx|slides]])
 *3:35-3:50, Overview of DICOM-RT - Greg Sharp ([[media:2012-01-09-sharp-dicomrt.pdf|slides]])
 *3:50-4:15, Slicer annotations for Quntitative Imaging Network (DICOM SR, AIM) - Andrey Fedorov ([[media:2012-01-09-fedorov-qin_slicer_annotation.pdf|slides]])

@@ Line 35: / Line 35: @@
 * Conversion issues between the representations
 ** Contour → Volume/Surface
 ** Manual or automatic
 * Are RT specific modules expanded during import or just on load in the treeview?

← Older revision		Revision as of 01:14, 11 January 2012
Line 37:		Line 37:
	** Manual or automatic		** Manual or automatic
	* Are RT specific modules expanded during import or just on load in the treeview?		* Are RT specific modules expanded during import or just on load in the treeview?
		+
		+	== Design questions==
		+	* How to add handling of the new entities in CTK?
		+	** Notifyable loadable module?
		+	* How to represent the data in Slicer? (which MRML nodes to use)
		+	* Conversion issues between the representations
		+	** Contour ? Volume/Surface
		+	** Manual or automatic
		+	* Are RT specific modules expanded during import or just on load in the treeview?
		+
		+	== Plan ==
		+	* Telecon with DCMTK group, CTK group
		+	** What can go reasonably in DCMTK should go there as lowest level toolkit
		+	*** Middle level addition for interpreting raw data
		+	** CTK
		+	*** Get relevant tags from RT/SR and insert them in database
		+	* Slicer extension
		+	** Hidden loadable module
		+	** Lower level register-observe method
		+	** Storage nodes, IO factory
		+	** Solve binding of the annotations to a volume
		+	* Representation
		+	** Contours
		+	*** Store contour series - vtkMRMLAnnotation...Node: PolyLine
		+	*** Hierarchy: Structure Set -> Structure -> Contour
		+	**** Hierarchy nodes that represent a relationship
		+	**** Transform graph: tree, Grouping: tree/graph?
		+
		+	== TBD ==
		+	* Image representation, multiple structures for a voxel
		+	* DICOM Metadata format in Slicer
		+	** Keep it in the file?
		+	*** We have the UID and the database -> we can get the file
		+	*** Caching may be implemented in CTK
		+	*** The file can be kept in memory
		+	*** Pointer in the vtkMRMLNode to a DCMTK object

← Older revision		Revision as of 22:17, 10 January 2012
Line 28:		Line 28:
	** What synergy is there with other efforts?		** What synergy is there with other efforts?
	* Are there specific issues that we can work out this week as a team?		* Are there specific issues that we can work out this week as a team?
		+
		+	== Design questions==
		+	* How to add handling of the new entities in CTK?
		+	** Notifyable loadable module?
		+	* How to represent the data in Slicer? (which MRML nodes to use)
		+	* Conversion issues between the representations
		+	** Contour → Volume/Surface
		+	** Manual or automatic
		+	* Are RT specific modules expanded during import or just on load in the treeview?