I am currently using 3D Slicer for a volume reconstruction of a series of ultrasound (US) image slices. In my slice controller (containing my live US image), I am unable to change the pixel spacing Volumes module.
For background, I am currently streaming my ultrasound data through a Plus Server (can email .xml file on request as I’m unable to attach it to this post) to 3D Slicer. I am using the OpenIGTLinkIF module (inside Slicer IGT) to connect 3D Slicer and the Plus Server. I proceeded to define the red slice controller as my image and attempted to use the Volumes module to get the proper pixel spacing.
Any help on the topic would be greatly appreciated.
Image spacing is embedded in the OpenIGTLink image message, therefore the value that you manually type is immediately overwritten when you get the next image. To have correct image spacing in Slicer, either adjust the OpenIGTLink sender to provide images with the appropriate spacing or in Slicer apply a transform to the image. See SlicerIGT tutorials for detailed instructions and explanations.
Thank you very much for your reply! I was originally using the SlicerIGT tutorials and was unable to find the specific lesson that relates to image spacing. I currently know that my pixel spacing along the transducer probe (marked axis) is 0.1 [mm] and the spacing along the depth of the image (far axis) is 0.085 [mm] but am unsure how to translate this into my .xml file or directly in Slicer. Any further direction on this issue would be greatly appreciated.
I would like to thank you for taking the time to respond to me initially and I look forward to your response!
I do have an Aurora NDI 6DOF EM tracker affixed to the probe on the side. I was going through lesson U-31 to compute the transformation between the tracker position and the image frame.
OK, if the probe is tracked and calibrated then you can follow U-33 and U-34 SlicerIGT tutorials about volume reconstruction. If you have difficulties in setting up your Plus configuration file, then you can post questions on the Plus issue tracker.
Thank you very much for the help, I have found out a solution to my problem! I modified the transformation matrix in the .xml to incorporate the scaling. For anyone else looking at this problem the way I set up my transformation matrix is shown in the figure attached.
