# Segment comparison - DICE coefficient is wrong!

**URL:** <https://discourse.slicer.org/t/segment-comparison-dice-coefficient-is-wrong/30000>\
**Category:** Support\
**Tags:** segmentation, slicerrt\
**Created:** [June 13, 2023, 2:54am UTC](https://discourse.slicer.org/t/segment-comparison-dice-coefficient-is-wrong/30000 "2023-06-13T02:54:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Teddy](https://avatars.discourse-cdn.com/v4/letter/t/da6949/32.png) [@Teddy](https://discourse.slicer.org/u/Teddy)\
**Post date:** [June 13, 2023, 2:54am UTC](https://discourse.slicer.org/t/segment-comparison-dice-coefficient-is-wrong/30000/1 "2023-06-13T02:54:41Z")

</div>

I used two same segments for comparison and calculate DICE using RTslicer module, but get the wrong result.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/4/b/4b70309ff501465b3286cfe0bb2ebe60f7294181.jpeg)

---

<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:** [June 13, 2023, 4:09am UTC](https://discourse.slicer.org/t/segment-comparison-dice-coefficient-is-wrong/30000/2 "2023-06-13T04:09:07Z")

</div>

Can’t reproduce. I am getting the expected 1.0. Make sure both segments have the same information. The simplest would be copying the contents of one segment to the other via the logical operators.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/c/9/c9902d973ac878591d9df649d6d053227c033367.jpeg)

---

<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:** [June 13, 2023, 4:14am UTC](https://discourse.slicer.org/t/segment-comparison-dice-coefficient-is-wrong/30000/3 "2023-06-13T04:14:40Z")

</div>

> [@Teddy](#):
>
> but get the wrong result.

Most likely during your segmentation you didn’t allow overlap between segments (by default changes modify all segments), hence there is no overlap between two segmentation and the reported value of 0.
