# Fill between slices, makes troubles!

**URL:** <https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706>\
**Category:** Support\
**Created:** [January 3, 2020, 4:15pm UTC](https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706 "2020-01-03T16:15:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![NoobForSlicer](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/noobforslicer/32/10900_2.png) [@NoobForSlicer](https://discourse.slicer.org/u/NoobForSlicer)\
**Post date:** [January 3, 2020, 4:15pm UTC](https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706/1 "2020-01-03T16:15:55Z")

</div>

![1](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/c/a/cac653b9f559103c87dcd5668cc6adb2e1a5dde2.png)

So here we see the segmenatin before the “fill between slices” and after I applied “fill between the slices”

IT appears to me that this does not only fill the empty slices that were not segmented, but instead changes the shape of already painted segmentation of slices.

How does it do so? What is the logic behind this?

If the slice has already been segmented, and the slice above and the slice above. Why does this function change them if it says "fill BETWEEN slices?

I assume it would fill an empty slice between the two existing segmentations of slices, not change the two existing ones?? Am I wrong?

How does it work?

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [January 3, 2020, 5:46pm UTC](https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706/2 "2020-01-03T17:46:38Z")

</div>

I wonder if this is somewhat related to the previous discussion about slice increments?

> [@View displays lag if pixel-spacing is small](https://discourse.slicer.org/t/view-displays-lag-if-pixel-spacing-is-small/9087/4):
>
> @lassoan, I tried and think the lag is no much due to change in the units, but simply the slider has only 0.001 mm increments, so slices do not get changed until the units incremented more than 0.001 mm (which will take 10 slices in this scenario). We will encounter small voxel data more and more through SlicerMorph. I wonder if it possible to tie the precision of the slice views (current seems only three significant digits), to image precision of the volume being displayed?

---

<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:** [January 3, 2020, 6:30pm UTC](https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706/3 "2020-01-03T18:30:08Z")

</div>

“Fill between slices” effect fills between parallel slices (along any of the 3 axes). See detailed description of the algorithm [here](http://insight-journal.org/browse/publication/977).

_Any_ editing operation in the Segment Editor will resample all the segments to the common labelmap geometry. If you have just imported a segment from another segmentation that had different geometry (higher resolution, different origin, or axis directions) then the segment will change upon the first editing operation. Segments are not immediately forced to the common image geometry to allow lossless moving/copying of segments between segmentations.

---

<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:** [November 23, 2022, 10:08pm UTC](https://discourse.slicer.org/t/fill-between-slices-makes-troubles/9706/4 "2022-11-23T22:08:30Z")

</div>

3 posts were split to a new topic: [Resample segments in segmentation using Python scripting](https://discourse.slicer.org/t/resample-segments-in-segmentation-using-python-scripting/26411)