Pixel Spacing for volume reconstruction of ultrasound images

Support
, ,
1

Hello I am new to 3D slicer.I have a telemed C5-2R60S-3 potable ultrasound probe and windows 11 Pro.I want to scan the abdomen and generate 3d volume.I have used plusApp & Slicer openIGTlinkIF to successfully visualize real-time ultrasound image in Slicer.When I check the details of active volume in slicer,I see pixel spacing (0.2,0.2,0.2) and image size (512,512,1).I also verified same pixel spacing(0.2,0.2,0.2) by exporting image as DICOM file and reading the DICOM metadata .
To check the correctness of pixel spacing:
From github I came to know that we can calculate image height (in mm)=total_pixels in y-axis (512)*pixel spacing in y-axis(0.2) =102.4mm.But I have set the depth of ultrasound as 150mm in echowaveII(telemed) software and I am assuming that image height should be near to 150 mm.

slicer_pixel_spac_issue
slicer_pixel_spac_issue1121×495 153 KB

slicer_pixel_spac_issue_dicom_data
slicer_pixel_spac_issue_dicom_data676×706 211 KB

I need help to calculate(or find) right pixel spacing and generate multi-frame 3d reconstruction in slicer.
Any help is really appreciated.I am not able to understand how I move forward from this point i.e. without right pixel spacing.
Thank You.

2

Hi, to reconstruct images in 3D, you need more information about ultrasound image position and orientation, not just spacing. Are you planning to use a position tracker attached to the ultrasound? Like in this video: (34) Real-time 3D ultrasound reconstruction using 3D Slicer + SlicerIGT - YouTube

3

Thank you for the reply.I am aware that calibration using position tracker provides transformation from ultrasound probe to ultrasound image frame leading to a fairly good ultrasound volume .But In my case,I only have position and orientation of ultrasound probe.
So I have 2 main parameters to be found for 3D reconstruction:
1)transformation from ultrasound probe to ultrasound image(or origin in ultrasound image)
2)pixel spacing
How can I find these parameters accurate enough in 3D slicer (or plusApp) ?