2012 Winter Project Week:BKPLUSSlicer - Revision history

Inorton at 16:35, 20 January 2012

2012-01-20T16:35:26Z

2012-01-13T16:20:56Z

Key Investigators

2012-01-13T15:41:21Z

2012-01-13T08:07:48Z

Key Investigators

2012-01-04T18:13:39Z

2012-01-04T18:13:28Z

2012-01-04T18:12:19Z

2012-01-04T18:10:39Z

2012-01-04T18:10:00Z

2012-01-04T17:52:56Z

Key Investigators

@@ Line 6: / Line 6: @@
 ==Key Investigators==
-* BWH: Isaiah Norton, Mehdi Moradi
+* BWH: Isaiah Norton, Mehdi Moradi, Matthew Toews
 * Queen's: Tamas Ungi

@@ Line 34: / Line 34: @@
 In meetings with the Queen's group and PLUS developers, we analyzed the architecture of the PLUS library to determine the best point of integration. A blueprint and initial connection handler code were created for the interface between the PLUS library and the BK SDK. The development is highly hardware dependent and will be completed/debugged back in Boston.
-We are implementing a subclass of the vtkPlusVideoSource code, following the template of vtkSonixVideoSource, to allow multi-mode (B-mode and RF-mode) acquisition with a flag setting. The point of interface is PlusBKOEMReceiver. This class inherits from both vtkVideoBuffer and IAcquisitionDataReceiver (private vendor class). This class handles the trickiest piece, which is the mutex locking and data transfer between the video buffer and the closed-source camera acquisition library.
+We are implementing a subclass of the vtkPlusVideoSource code, following the template of vtkSonixVideoSource, to allow multi-mode (B-mode and RF-mode) acquisition with a flag setting. The point of interface is PlusBKOEMReceiver. This class inherits from both vtkVideoBuffer and IAcquisitionDataReceiver (from private BK SDK). This class handles the trickiest piece, which is the mutex locking and data transfer between the video buffer and the closed-source camera acquisition library.
 </div>
 </div>

@@ Line 32: / Line 32: @@
 <h3>Progress</h3>
-In meetings with the Queen's group and PLUS developers, we analyzed the architecture of the PLUS library. A blueprint and pseudocode were created for the interface between the PLUS library and the BK SDK. The development is highly hardware dependent and will be completed back in Boston.
+In meetings with the Queen's group and PLUS developers, we analyzed the architecture of the PLUS library to determine the best point of integration. A blueprint and initial connection handler code were created for the interface between the PLUS library and the BK SDK. The development is highly hardware dependent and will be completed/debugged back in Boston.
 </div>
 </div>

@@ Line 32: / Line 32: @@
 <h3>Progress</h3>
 </div>
 </div>

@@ Line 2: / Line 2: @@
 <gallery>
 Image:PW-SLC2012.png|[[2012_Winter_Project_Week#Projects|Projects List]]
-File:bk.png|
+File:bk.PNG|
 </gallery>

@@ Line 12: / Line 12: @@
 <h3>Objective</h3>
-The goal is to integrate and streamline tracked data logging from the BK ultrasound (specifically RF data) using Slicer and PLUS. This will facilitate use of the BK system for on- and off-line visualization and data analysis.
+The goal is to integrate and streamline tracked data logging from the BK ultrasound (specifically RF data) using Slicer and PLUS. This will facilitate use of the BK system for on- and off-line visualization and data analysis. In certain clinical applications in BWH AMIGO that use the BK system, such as prostate interventions and brain tumor resection procedures, real time ultrasound-based tissue typing is a very useful addition. Tracking and streaming of the RF data to a high end PC is essential for these purposes.
@@ Line 22: / Line 22: @@
 <h3>Approach, Plan</h3>
 </div>