# Changing the default algorithm for model creation in segment editor

**URL:** <https://discourse.slicer.org/t/changing-the-default-algorithm-for-model-creation-in-segment-editor/40657>\
**Category:** Support\
**Created:** [December 12, 2024, 5:14pm UTC](https://discourse.slicer.org/t/changing-the-default-algorithm-for-model-creation-in-segment-editor/40657 "2024-12-12T17:14:19Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [December 13, 2024, 5:30am UTC](https://discourse.slicer.org/t/changing-the-default-algorithm-for-model-creation-in-segment-editor/40657/2 "2024-12-13T05:30:16Z")

</div>

Still flying edges is used in the Slicer Preview Release. Surface nets is the new, faster option. We agree that we should use that by default ([Bad performance when segmenting 11GB micro-CT - #8 by pieper](https://discourse.slicer.org/t/bad-performance-when-segmenting-11gb-micro-ct/38362/8)). We haven’t decided if we should do it in Slicer 5.8 or later, but I think it is better to do it now. I’ve added an issue to track this:

> <https://github.com/Slicer/Slicer/issues/8093>
>
> As discussed, we should use surface nets to generate closed surface representati…on from binary labelmap represenation in segmentations. See the discussion at https://discourse.slicer.org/t/bad-performance-when-segmenting-11gb-micro-ct/38362/8?u=lassoan

---

_[View the full topic](https://discourse.slicer.org/t/changing-the-default-algorithm-for-model-creation-in-segment-editor/40657)._