|
|
| (7 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | = Introduction =
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:4DUltrasound_4D_US here]</font></big> |
| − | The following graph shows how the Ultrasound scanner will be connected with 3D Slicer using the IGT Link
| |
| − | [[Image:US_openIGTLink.png|frame|none|Transfer Image from Ultrasound]]
| |
| − | | |
| − | To the right the '''Ultrasound Server''' is retrieving images based on the position of the scanner.
| |
| − | The '''computer's server software''' supports an interface to translate the scanning planes and to retrieve and send images from the scanner.
| |
| − | | |
| − | Then the data is transferred over the network using the '''OpenIGTLink''', the network protocol of 3D Slicer.
| |
| − | | |
| − | Finally '''3D Slicer''' visualizes the data and sends tracking commands back over the link to update the viewing plane.
| |
| − | | |
| − | = Detailed Process =
| |
| − | == Image Acquisition ==
| |
| − | This is the region that has to be designed by the developers of the scanner.
| |
| − | | |
| − | == Data Transfer ==
| |
| − | There are two data transfers involved in this process, ''Image Transfers'' from the scanner to slicer and ''command transfers'' into the revers direction.
| |
| − | | |
| − | === Image Transfers === | |
| − | To transfer an image from a server to 3D Slicer the following objects have to considered:
| |
| − | #Open connection to 3D Slicer
| |
| − | #Data Creation
| |
| − | ##Create ImageData buffer on server
| |
| − | ##Create MRML Node holding a ImageData in Slicer connected to the ImageData on the server
| |
| − | #Data Transfer
| |
| − | ##Fill ImageData buffer on Server with US Data
| |
| − | ##Send Data over Link
| |
| − | | |
| − | By now the MRML node's image data is updated and ready to visualize.
| |
| − | | |
| − | === Command Transfer ===
| |
| − | Tracking commands are sent using the command structure supported by slicer's openIGT Link
| |
| − | | |
| − | == Data Visualization ==
| |
| − | To Transfer 3D images from the scanner to Slicer we make use of openIGT Link
| |
| − | | |
| − | = Interfaces =
| |
| − | | |
| − | | |
| − | = Misc =
| |
| − | A tutorial to get openIGT Link running with 3D Slicer and 4D volume rendering can be found [[Slicer3:openIGT_Tutorial_For_4D_Volume_Rendering_Data|here]].
| |
| − | | |
| − | | |
| − | = Media =
| |
| − | [[Image:US_Photoseries_1.png|thumb|200px|none|Scanner working with Slicer3]]
| |
| − | [[Image:US_Photoseries_2.png|thumb|200px|left|Scanner working with Slicer3]]
| |
| − | [[Image:US_Photoseries_3.png|thumb|200px|left|Scanner working with Slicer3]]
| |
| − | [[Image:US_Photoseries_4.png|thumb|200px|left|Scanner working with Slicer3]]
| |
