# Slicer 5.6.2 will flash back when it calculated Hausdorff metric and Dice metric in SegmentComparison module

**URL:** <https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552>\
**Category:** Support\
**Created:** [October 6, 2024, 8:37am UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552 "2024-10-06T08:37:22Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alice914](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alice914/32/77819_2.png) [@Alice914](https://discourse.slicer.org/u/Alice914)\
**Post date:** [October 6, 2024, 8:37am UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/1 "2024-10-06T08:37:22Z")

</div>

Slicer will flash back when calculating Hausdorff distance metrics and dice metrics for the same layer in two different images using slicer’s radiotherapy-segmentcomparison. I tried to reduce the size of the image and run it on two different computers, but it still didn’t work. What is the reason for this? Could you give me some suggestions? Thank you

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [October 7, 2024, 8:17am UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/2 "2024-10-07T08:17:51Z")

</div>

What does it mean “flash back”? Can you please describe the exact steps you take, what you expect, and what happens instead exactly?

Also, what does it mean “same layer in two different images”? Are you working with 2D images?

---

<div class="post-metadata">

**Author:** ![Alice914](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alice914/32/77819_2.png) [@Alice914](https://discourse.slicer.org/u/Alice914)\
**Post date:** [October 8, 2024, 8:41am UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/3 "2024-10-08T08:41:11Z")

</div>

1.’flash back’ means software will automatically quit suddenly when you are using.

2.The extact steps:

Load images(SliceMorph- input and output- image stack)

Segment images(Segment Editor- Add segment for two images)

Calculate Dice metric (Radiotherapy - Segment Comparison)

3.My goal is across ‘segment comparison’ module gains images’ Dice metric and Hausdorff. This module would give results of the calculation in software in the past, but now the software will automatically exit when ‘Compute Hausdorff distance’ is clicked.

 ![img_v3_02f7_0834eea1-d74d-4155-a122-4f4fbd78c21g](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/3/b/3b6dd116e96183d5163e14824df63e03f00927c5.jpeg)

4.I hope this issues that software will automatically exit when I use the function of segment comparison can be solved

5.Same layer looks at green line in the image.

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

6.My imaging is phase contrast and fluorescence. They both consist of multiple pieces of 2d images.

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [October 8, 2024, 8:59am UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/4 "2024-10-08T08:59:09Z")

</div>

> [@Alice914](#):
>
> 1.’flash back’ means software will automatically quit suddenly when you are using

OK thanks. It is called a crash.

Unfortunately it is not clear to me if you are really working with 3D images. I was asking because most tools in Slicer are not designed to run on 2D data. Could you upload this MRB scene and share it?

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [October 10, 2024, 11:24am UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/5 "2024-10-10T11:24:51Z")

</div>

Thanks for sending the scene.

> [@cpinter](#):
>
> Unfortunately it is not clear to me if you are really working with 3D images. I was asking because most tools in Slicer are not designed to run on 2D data

It turns out this is the case. Slicer is designed to work on 3D data. I suggest doing real 3D segmentations and comparing those.

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

The fact that it crashes is quite bad, but if the tools are not used in a way they are intended, unexpected things may happen.

---

<div class="post-metadata">

**Author:** ![Alice914](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alice914/32/77819_2.png) [@Alice914](https://discourse.slicer.org/u/Alice914)\
**Post date:** [October 10, 2024, 2:08pm UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/6 "2024-10-10T14:08:18Z")

</div>

Thank you very much for answering my questions on your busy schedule! I would like to ask about fluorescence slicing to increase the number of picture sheets to form a 3d image, why is this not possible? Can phase contrast this kind of image be used in 3d slicer?

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [October 10, 2024, 3:40pm UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/7 "2024-10-10T15:40:38Z")

</div>

I’m sorry I don’t quite understand the question, I’m not an expert in image aquisition or reconstruction. However, I have the feeling that Slicer cannot really help with acquiring better images. It can load and process images but it is a later stage. Maybe someone else will be able to help. Or if you explain it more, maybe I will understand.

---

<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 10, 2024, 4:41pm UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/8 "2024-10-10T16:41:34Z")

</div>

@Alice914 it sounds like you are doing microscopy analysis. Slicer would be most helpful for confocal, light sheet, or other natively 3D acquisitions (based on my limitied experience with microscopy). It’s not a main application, but you might checkout [GitHub - gaoyi/SlicerBigImage: Large (GB and above) scale microscopic image computing using 3D Slicer](https://github.com/gaoyi/SlicerBigImage) to get an idea what’s possible.

---

<div class="post-metadata">

**Author:** ![Alice914](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alice914/32/77819_2.png) [@Alice914](https://discourse.slicer.org/u/Alice914)\
**Post date:** [October 11, 2024, 2:34am UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/9 "2024-10-11T02:34:44Z")

</div>

Thank you a lot!! Maybe it is image problem. Now I get it that 2d image is not suitable in 3d slicer

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [October 11, 2024, 1:26pm UTC](https://discourse.slicer.org/t/slicer-5-6-2-will-flash-back-when-it-calculated-hausdorff-metric-and-dice-metric-in-segmentcomparison-module/39552/10 "2024-10-11T13:26:44Z")

</div>

Well, some 3D algorithms may not work for simgle-slice data, like you saw with segment comparison.

But if you can extend the segmentation to 3D, then it will probably run. Is it important for you to have a different segment on each slice?