Events:2011-08-24-DICOM-ITK-Discussion - Revision history

Aylward: /* Yoo Directive (Actual tasks moving forward) */

2011-08-25T15:43:52Z

Yoo Directive (Actual tasks moving forward)

Aylward at 15:43, 25 August 2011

2011-08-25T15:43:10Z

Aylward: /* DICOM/Wrapping in ITKv4 */

2011-08-25T15:39:50Z

DICOM/Wrapping in ITKv4

Aylward: /* DICOM/Wrapping in ITKv4 */

2011-08-25T15:38:23Z

DICOM/Wrapping in ITKv4

Aylward: /* DICOM/Wrapping in ITKv4 */

2011-08-25T15:37:44Z

DICOM/Wrapping in ITKv4

Aylward: /* DICOM/Wrapping in ITKv4 */

2011-08-25T15:30:56Z

DICOM/Wrapping in ITKv4

Aylward: /* Meeting notes */

2011-08-25T15:18:05Z

Meeting notes

Aylward at 15:01, 25 August 2011

2011-08-25T15:01:52Z

Aylward at 14:52, 25 August 2011

2011-08-25T14:52:03Z

Aylward at 14:47, 25 August 2011

2011-08-25T14:47:12Z

@@ Line 73: / Line 73: @@
 * DCMTK moving forward
 ** Get integrated with ITK
-** Drop DICOM RT and Diffusion MRI in GDCM (get closure)
+** Get rapid closure on DICOM RT and Diffusion MRI in GDCM
 * Steve, Stephen, and Alex create a committee to solve
 ** Roadmap, Define deliverables, Validation
 ** Use wiki and emails to keep Terry and Community informed
 ** Dan and Bill can be part of the solution (pending Jim M's "approval")

@@ Line 13: / Line 13: @@
 **integration of the diffusion work by Hans, Vince, Xioadong et al.
-= Attendees =
+= ITKv4 / NA-MIC Meeting =
-* Ron, Steve P, Will, Jim, Terry, Alex, Dan, Gaetan, Bill Ryan
+* August 25, 10:30am
-= Meeting notes =
+== Meeting notes ==
 * Agenda
 *# Update from Mayo on DICOM effort
@@ Line 23: / Line 25: @@
-== Slicer4 Point of View ==
+=== Slicer4 Point of View ===
 * See notes above
 * Consistent plan for quite some time
@@ Line 44: / Line 46: @@
 *** NA-MIC: Not trying for DCMTK and GDCM to co-exist - concern is inconsistent interpretation of data
-== Update from Mayo ==
+=== Update from Mayo ===
 * Process
 *# Create programmatic query
@@ Line 55: / Line 57: @@
 ** Application is responsible for DICOM management
-== DICOM/Wrapping in ITKv4 ==
+=== DICOM/Wrapping in ITKv4 ===
-=== Proposed ===
+==== Proposed ====
 * Moving forward (Alex)
 ** Don't do DICOM networking (PACS) in GDCM
@@ Line 68: / Line 70: @@
 ** DCMTK (including networking) into ITKv4 via a module
 *** Extract things from CTK
-=== Yoo Directive (Actual tasks moving forward) ===
+==== Yoo Directive (Actual tasks moving forward) ====
 * DCMTK moving forward
 ** Get integrated with ITK

@@ Line 56: / Line 56: @@
 == DICOM/Wrapping in ITKv4 ==
 * Moving forward (Alex)
 ** Don't do DICOM networking (PACS) in GDCM
@@ Line 67: / Line 68: @@
 ** DCMTK (including networking) into ITKv4 via a module
 *** Extract things from CTK
-=== Yoo Directive ===
+=== Yoo Directive (Actual tasks moving forward) ===
 * DCMTK moving forward
 ** Get integrated with ITK
-** Drop DICOM RT and Diffusion MRI in GDCM
+** Drop DICOM RT and Diffusion MRI in GDCM (get closure)
 * Steve, Stephen, and Alex create a committee to solve
-** Define deliverables
+** Roadmap, Define deliverables, Validation
 ** Use wiki and emails to keep Terry and Community informed
 ** Dan and Bill can be part of the solution (pending Jim M's "approval")

@@ Line 67: / Line 67: @@
 ** DCMTK (including networking) into ITKv4 via a module
 *** Extract things from CTK
-* Yoo Directive
+=== Yoo Directive ===
-** DCMTK moving forward
+* DCMTK moving forward
-*** Get integrated with ITK
+** Get integrated with ITK
-*** Drop DICOM RT and Diffusion MRI in GDCM
+** Drop DICOM RT and Diffusion MRI in GDCM
-** Steve, Stephen, and Alex create a committee to solve
+* Steve, Stephen, and Alex create a committee to solve
-*** Define deliverables
+** Define deliverables
-*** Use wiki and emails to keep Terry and Community informed
+** Use wiki and emails to keep Terry and Community informed
-*** Dan and Bill can be part of the solution (pending Jim M's "approval")
+** Dan and Bill can be part of the solution (pending Jim M's "approval")

← Older revision		Revision as of 15:37, 25 August 2011
Line 67:		Line 67:
	** DCMTK (including networking) into ITKv4 via a module		** DCMTK (including networking) into ITKv4 via a module
	*** Extract things from CTK		*** Extract things from CTK
		+	* Yoo Directive
		+	** DCMTK moving forward
		+	*** Get integrated with ITK
		+	*** Drop DICOM RT and Diffusion MRI in GDCM
		+	** Steve, Stephen, and Alex create a committee to solve
		+	*** Define deliverables
		+	*** Use wiki and emails to keep Terry and Community informed
		+	*** Dan and Bill can be part of the solution (pending Jim M's "approval")

@@ Line 63: / Line 63: @@
 ** Redirect PACS support to wrapping
 * Moving forward (Dan)
-** DCMTK (including network) into ITKv4 via a module
+** DICOM expertise consulting

@@ Line 42: / Line 42: @@
 *** Testing: NA-MIC using AMIGO suite for networking
 *** Size, licensing, and software-revision-control of DCMTK: NA-MIC reviewed and has helped them come up to speed
 == Update from Mayo ==
@@ Line 50: / Line 51: @@
 ** No GUI
 ** Tool for an application developer
 == DICOM/Wrapping in ITKv4 ==
+* Moving forward (Alex)

@@ Line 1: / Line 1: @@
 =Slicer ITK Dicom=
 The following are talking points for a phone call on 8-25-2011
-*Dicom query-retrieve networking without a UI isn't much help (there is almost always a human-in-the-loop to decide which study or series to select).
+* Dicom query-retrieve networking without a UI isn't much help (there is almost always a human-in-the-loop to decide which study or series to select).
-*Since ITK isn't in the UI business so there is no need for ITK dicom networking support.
+* Since ITK isn't in the UI business so there is no need for ITK dicom networking support.
-*/Interpreting dicom/ on the other hand, is right in the ITK sweet spot. That is, converting dicom datasets into itk images (or meshes, etc) is a big unsolved problem where applications need a lot of help.
+* /Interpreting dicom/ on the other hand, is right in the ITK sweet spot. That is, converting dicom datasets into itk images (or meshes, etc) is a big unsolved problem where applications need a lot of help.
 * On one of the ITK calls it was discussed that the application might point itk to a directory tree and ask, essentially, for a list of possible interpretations of that data.  For example, by looking at a directory you might get back a data structure that says that there are two DWI volumes that could be loaded or you could load them as 60 individual volumes, or you could load them as several thousand 2D slices.
 * On the GUI and networking side, very good progress has been made in the combination of ctk with dcmtk and Qt.  It's not ready for prime time, and there are no assurances about how future development will go.
@@ Line 26: / Line 26: @@
 * See notes above
 * Consistent plan for quite some time
 == Update from Mayo ==
-−
+*
 == DICOM/Wrapping in ITKv4 ==
+*