# OCT b-scan thickness is not being found on load

**URL:** <https://discourse.slicer.org/t/oct-b-scan-thickness-is-not-being-found-on-load/32273>\
**Category:** Support\
**Tags:** dicom\
**Created:** [October 17, 2023, 3:09pm UTC](https://discourse.slicer.org/t/oct-b-scan-thickness-is-not-being-found-on-load/32273 "2023-10-17T15:09:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Banghart](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@Mark\_Banghart](https://discourse.slicer.org/u/Mark_Banghart)\
**Post date:** [October 17, 2023, 3:09pm UTC](https://discourse.slicer.org/t/oct-b-scan-thickness-is-not-being-found-on-load/32273/1 "2023-10-17T15:09:41Z")

</div>

We have a number of legacy DICOM files that we would like to view in slicer. The files load with drag and drop. The user selects volume and the OCT is displayed. The pixel dimensions for the x and y dimensions are filled in correctly in slicer. The thickness for the b-scans (z axis) is set to 1. The DICOM has the b-scan thickness in the header. I can get it with the following python code.

z\_spacing = dcm.SharedFunctionalGroupsSequence[0].PixelMeasuresSequence[0].SliceThickness

Where is slicer looking for the OCT thickness? If I know where slicer is looking for it I can modify the DICOM so that they load in slicer with the b-scan thickness.  
Thanks  
Mark

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [October 17, 2023, 5:09pm UTC](https://discourse.slicer.org/t/oct-b-scan-thickness-is-not-being-found-on-load/32273/2 "2023-10-17T17:09:35Z")

</div>

Generally Slicer is only concerned with spacing between Slices, so you need to make sure the ImagePositionPatient is defined for each slice to make a volume.