# Slice Thickness for multi-frame ultrasound

**URL:** <https://discourse.slicer.org/t/slice-thickness-for-multi-frame-ultrasound/23617>\
**Category:** Support\
**Tags:** ultrasound\
**Created:** [May 27, 2022, 10:49pm UTC](https://discourse.slicer.org/t/slice-thickness-for-multi-frame-ultrasound/23617 "2022-05-27T22:49:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![svesal](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/svesal/32/13777_2.png) [@svesal](https://discourse.slicer.org/u/svesal)\
**Post date:** [May 27, 2022, 10:49pm UTC](https://discourse.slicer.org/t/slice-thickness-for-multi-frame-ultrasound/23617/1 "2022-05-27T22:49:45Z")

</div>

Hi,

I am just new to 3D slicer and I wanted to ask one question. I have a set of raw ultrasound data (cineloop) and I have the pixel spacing information (0.03x0.03) and not slice thickness for volumetric reconstruction. It seems the voxels are not isotropic, so when I reconstruct the volume the sagittal view is prefect (with pixel spacing of (0.03x0.03.0x0.03)) but the axial and coronal plane looks not correct (compressed, thin).

I wanted to ask, how I can compute the slice thickness (z-axis) if I have only pixel-spacing info for x and y axes?

Thank you,  
Best,

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 27, 2022, 11:29pm UTC](https://discourse.slicer.org/t/slice-thickness-for-multi-frame-ultrasound/23617/2 "2022-05-27T23:29:52Z")

</div>

Was the image series acquired by sliding the transducer on the patient’s body?

Was a position tracker used to record accurate pose of the transducer for each image slice?

---

<div class="post-metadata">

**Author:** ![svesal](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/svesal/32/13777_2.png) [@svesal](https://discourse.slicer.org/u/svesal)\
**Post date:** [May 28, 2022, 12:18am UTC](https://discourse.slicer.org/t/slice-thickness-for-multi-frame-ultrasound/23617/3 "2022-05-28T00:18:14Z")

</div>

Hi Lasso,

The ultrasound images acquired using side-fire probe! these are micro-ultrasound images similar to transrectal ultrasound after inserting the probe into rectum to capture prostate gland images.

The pose information is not there, since we had only processed RF data.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/8/e/8e3301ec52cfb084c06bee9f73bd651340267d69.jpeg)

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 28, 2022, 12:30am UTC](https://discourse.slicer.org/t/slice-thickness-for-multi-frame-ultrasound/23617/4 "2022-05-28T00:30:00Z")

</div>

Which imaging system is this? A commercial device or a custom-built research tool?

Was the probe rotated or translated during acquisition? Was it moved by a motor or just freehand?

Is the `image position patient` and `image orientation patient` tags are set correctly for each frame?