# Not equally spaced error... solution?

**URL:** https://discourse.slicer.org/t/not-equally-spaced-error-solution/35710
**Category:** Support
**Created:** [April 24, 2024, 4:05pm UTC](https://discourse.slicer.org/t/not-equally-spaced-error-solution/35710 "2024-04-24T16:05:08Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [April 24, 2024, 4:45pm UTC](https://discourse.slicer.org/t/not-equally-spaced-error-solution/35710/2 "2024-04-24T16:45:37Z")

</div>

That may not be a “problem”, just a description of the data with a message about how Slicer addressed it. Have a look at the thread below and get back if there’s something else going on.

> [@Understanding CT Image spacing and Acquisition geometry regularization](https://discourse.slicer.org/t/understanding-ct-image-spacing-and-acquisition-geometry-regularization/19001):
>
> Dear all, "Images are not equally spaced (a difference of 0.6 vs 0.3 was detected)’ Why does this error occur? What causes the acquisition of acquired irregular geometry? is it something to do with CT machine, protocol, technique or just a problem with exporting the data? with Acquisition geometry regularization correction transform applied, I tried to harden the transformation and I expected the corrected version of the image to persist but it changed to the original? is this the expected b…

---

_[View the full topic](https://discourse.slicer.org/t/not-equally-spaced-error-solution/35710)._