Slicer3:BrainLabModule - Revision history

Hliu at 03:17, 27 April 2010

2010-04-27T03:17:55Z

Hliu: /* Progress */

2010-04-12T16:56:38Z

Progress

Hliu: /* Progress */

2010-04-12T16:54:51Z

Progress

Hliu: /* Progress */

2010-04-12T16:51:06Z

Progress

Hliu: /* Progress */

2010-04-12T16:42:48Z

Progress

Hliu: /* Progress */

2010-04-12T16:32:02Z

Progress

Hliu: /* Progress */

2010-04-12T16:17:37Z

Progress

Hliu: /* Progress */

2010-04-12T16:07:35Z

Progress

Hliu: /* Progress */

2010-04-12T16:04:14Z

Progress

Hliu: /* Progress */

2010-04-12T14:55:39Z

Progress

@@ Line 1: / Line 1: @@
 [[Slicer3:Developers#Quick_Links_to_Slicer3_Projects|Back to '''Slicer Projects Page''']]
 = Aim =
-BrainLab (http://www.brainlab.com) has recently introduced a customized client/server architecture called '''VectorVision Link (VV Link)''' to communicate with external IGT environment. This software API, open but not free, allows other programs to acquire tracking information and images from the BrainLab system. We propose to create a comprehensive workflow to interface 3D Slicer to BrainLab system and to use it for research. Specifically, we create simplified steps for neurosurgeons to use Slicer to perform some research in DTI visualization in OR while BrainLab is used as the primary navigation tool. Here is the scenario:
+Brainlab (http://www.brainlab.com) has recently introduced a customized client/server architecture called '''VectorVision Link (VV Link)''' to communicate with external IGT environment. This software API, open but not free, allows other programs to acquire tracking information and images from the BrainLab system. We propose to create a comprehensive workflow to interface 3D Slicer to Brainlab system and to use it for research. Specifically, we create simplified steps for neurosurgeons to use Slicer to perform some research in DTI visualization in OR while Brainlab is used as the primary navigation tool. Here is the scenario:
-BrainLab system will still run as usual; we won't install any software and hardware on the BrainLab computer and won't affect its FDA status either. Slicer runs on a different computer. These two computers will be connected to each other using a network or router. During surgical procedures, the BrainLab sends real-time tracking data and/or images to Slicer. The tracking information may be used to seed dynamic DTI visualization in Slicer.
+Brainlab system will still run as usual; we won't install any software and hardware on the Brainlab computer and won't affect its FDA status either. Slicer runs on a different computer. These two computers will be connected to each other using a network or router. During surgical procedures, the BrainLab sends real-time tracking data and/or images to Slicer. The tracking information may be used to seed dynamic DTI visualization in Slicer.
 = Research Plan =
 Our workflow will include the following steps:
-#Set up connection between BrainLab and Slicer
+#Set up connection between Brainlab and Slicer
 #Load a scene (default or user specific) into Slicer
-#Navigate with DTI visualization in Slicer as the surgeon performs tracking with BrainLab
+#Navigate with DTI visualization in Slicer as the surgeon performs tracking with Brainlab
-This will hopefully help the surgeon efficiently integrate Slicer with BrainLab. We will implement the workflow by developing a Slicer module called '''BrainLabModule'''. This interactive module uses OpenIGTLink (http://www.na-mic.org/Wiki/index.php/OpenIGTLink) for data communication between BrainLab and Slicer, and uses Fiducial, DTMRI and FiducialSeeding modules for DTI visualization. Also, it uses existing Slicer functions to load MRML scenes.
+This will hopefully help the surgeon efficiently integrate Slicer with Brainlab. We will implement the workflow by developing a Slicer module called '''BrainlabModule'''. This interactive module uses OpenIGTLink (http://www.na-mic.org/Wiki/index.php/OpenIGTLink) for data communication between BrainLab and Slicer, and uses Fiducial, DTMRI and FiducialSeeding modules for DTI visualization. Also, it uses existing Slicer functions to load MRML scenes.
-The development of BrainLabModule will be completed in two phases. In the first phase, a BrainLab simulator will be created. That is, a sequence of synthetic tracking points (not from BrainLab system) will be streamed to Slicer where fiducial-driven DTI visualization will be performed. In the second phase, a real BrainLab system will be needed to test the entire workflow. Upon completion, both modes (Simulator and BrainLab) will co-exist in the module; the user may choose which mode to execute.
+The development of BrainlabModule will be completed in two phases. In the first phase, a Brainlab simulator will be created. That is, a sequence of synthetic tracking points (not from BrainLab system) will be streamed to Slicer where fiducial-driven DTI visualization will be performed. In the second phase, a real BrainLab system will be needed to test the entire workflow. Upon completion, both modes (Simulator and Brainlab) will co-exist in the module; the user may choose which mode to execute.
 Both modes are accompanied by training materials and documentation to ensure usability.
@@ Line 29: / Line 29: @@
 * Week of 04/05/2010
 ** Work '''DONE''':
-*** The user interface (GUI) has been enhanced and implemented for the Connect Step where the network communication between BrainLabModule and a tracking source is going to be set up. Now we have a working version of Connect Step for tracking simulation. After few configurations, simulated tracking data will be streamed to OpenIGTLink module in Slicer once the Connect button is clicked. The data streaming process may be stopped by clicking the Close button.
+*** The user interface (GUI) has been enhanced and implemented for the Connect Step where the network communication between BrainlabModule and a tracking source is going to be set up. Now we have a working version of Connect Step for tracking simulation. After few configurations, simulated tracking data will be streamed to OpenIGTLink module in Slicer once the Connect button is clicked. The data streaming process may be stopped by clicking the Close button.
-*** Since the connection between BrainLabModule and the tracking source is always on, it's a good idea to have a separate thread to handle the network communication. This will improve the Slicer response to the user interaction. The thread will be stopped by clicking the Close button in the interface.
+*** Since the connection between BrainlabModule and the tracking source is always on, it's a good idea to have a separate thread to handle the network communication. This will improve the Slicer response to the user interaction. The thread will be stopped by clicking the Close button in the interface.
 *** A stream of simulated tracking data points may be generated inside memory or read from a file. The file IO is chosen since in the future tracking data sets of real surgical cases, which are usually saved in a file, may be used for post-surgical re-examination or just demonstration only.
 ** To do list:
-*** OpenIGTLink module is now configured through its interface. This configuration will be required to be implemented programmatically in the C++ code of BrainLabModule.
+*** OpenIGTLink module is now configured through its interface. This configuration will be required to be implemented programmatically in the C++ code of BrainlabModule.
 *** Implementation of Load Step and Navigate Step will be executed next week.
@@ Line 41: / Line 41: @@
 = Dependency =
-The following modules are required for BrainLab module to work properly:<br>
+The following modules are required for Brainlab module to work properly:<br>
 Fiducial<br>
 OpenIGTLink<br>

@@ Line 31: / Line 31: @@
 *** The user interface (GUI) has been enhanced and implemented for the Connect Step where the network communication between BrainLabModule and a tracking source is going to be set up. Now we have a working version of Connect Step for tracking simulation. After few configurations, simulated tracking data will be streamed to OpenIGTLink module in Slicer once the Connect button is clicked. The data streaming process may be stopped by clicking the Close button.
 *** Since the connection between BrainLabModule and the tracking source is always on, it's a good idea to have a separate thread to handle the network communication. This will improve the Slicer response to the user interaction. The thread will be stopped by clicking the Close button in the interface.
-*** A stream of simulated tracking data points may be generated inside memory or read from a file. The file IO is chosen since in the future tracking data sets of real surgical cases, which are usually saved in a file, may be used for re-examination or demonstration.
+*** A stream of simulated tracking data points may be generated inside memory or read from a file. The file IO is chosen since in the future tracking data sets of real surgical cases, which are usually saved in a file, may be used for post-surgical re-examination or just demonstration only.
 ** To do list:
 *** OpenIGTLink module is now configured through its interface. This configuration will be required to be implemented programmatically in the C++ code of BrainLabModule.

@@ Line 29: / Line 29: @@
 * Week of 04/05/2010
 ** Work '''DONE''':
-*** The user interface (GUI) has been enhanced and implemented for the Connect Step where the network communication between BrainLabModule and a tracking source is going to be set up. Now we have a working version of Connect Step for tracking simulation. After few configurations, simulated tracking data will be streamed to OpenIGTLink once the Connect button is clicked. The data streaming process may be stopped by clicking the Close button.
+*** The user interface (GUI) has been enhanced and implemented for the Connect Step where the network communication between BrainLabModule and a tracking source is going to be set up. Now we have a working version of Connect Step for tracking simulation. After few configurations, simulated tracking data will be streamed to OpenIGTLink module in Slicer once the Connect button is clicked. The data streaming process may be stopped by clicking the Close button.
 *** Since the connection between BrainLabModule and the tracking source is always on, it's a good idea to have a separate thread to handle the network communication. This will improve the Slicer response to the user interaction. The thread will be stopped by clicking the Close button in the interface.
 *** A stream of simulated tracking data points may be generated inside memory or read from a file. The file IO is chosen since in the future tracking data sets of real surgical cases, which are usually saved in a file, may be used for re-examination or demonstration.

@@ Line 31: / Line 31: @@
 *** The user interface (GUI) has been enhanced and implemented for the Connect Step where the network communication between BrainLabModule and a tracking source is going to be set up. Now we have a working version of Connect Step for tracking simulation. After few configurations, simulated tracking data will be streamed to OpenIGTLink once the Connect button is clicked. The data streaming process may be stopped by clicking the Close button.
 *** Since the connection between BrainLabModule and the tracking source is always on, it's a good idea to have a separate thread to handle the network communication. This will improve the Slicer response to the user interaction. The thread will be stopped by clicking the Close button in the interface.
-*** Read simulated tracking data from a file and send them to OpenIGTLink.
+*** A stream of simulated tracking data points may be generated inside memory or read from a file. The file IO is chosen since in the future tracking data sets of real surgical cases, which are usually saved in a file, may be used for re-examination or demonstration.
 ** To do list:
-*** We now configure OpenIGTLink module through its interface. Need the configuration implemented programmatically in the C++ code of BrainLabModule.
+*** OpenIGTLink module is now configured through its interface. This configuration will be required to be implemented programmatically in the C++ code of BrainLabModule.
 * Week of 03/29/2010

@@ Line 29: / Line 29: @@
 * Week of 04/05/2010
 ** Work '''DONE''':
-*** The user interface (GUI) has been enhanced and implemented for the Connect Step. Now we have a working version of Connect Step for tracking simulation. After few configurations, simulated tracking data will be streamed to OpenIGTLink once the Connect button is clicked. The data streaming processing may stopped by clicking the Close button.
+*** The user interface (GUI) has been enhanced and implemented for the Connect Step where the network communication between BrainLabModule and a tracking source is going to be set up. Now we have a working version of Connect Step for tracking simulation. After few configurations, simulated tracking data will be streamed to OpenIGTLink once the Connect button is clicked. The data streaming process may be stopped by clicking the Close button.
-*** Create a thread to handle the connection between BrainLab module with a tracking source.
+*** Since the connection between BrainLabModule and the tracking source is always on, it's a good idea to have a separate thread to handle the network communication. This will improve the Slicer response to the user interaction. The thread will be stopped by clicking the Close button in the interface.
 *** Read simulated tracking data from a file and send them to OpenIGTLink.
 ** To do list:

@@ Line 27: / Line 27: @@
 =Progress=
-* Week of 03/29/10
+* Week of 04/05/2010
 ** Ron, Noby and Haiying met at Ron's office to discuss the specs of the module and time frame for implementation.
 ** Haiying completed the [[Slicer3:BrainLabModule:Workflow|workflow.]]