# Ideal hardware configuration for high quality segmentations

**URL:** <https://discourse.slicer.org/t/ideal-hardware-configuration-for-high-quality-segmentations/9281>\
**Category:** Support\
**Tags:** segmentation\
**Created:** [November 24, 2019, 9:02am UTC](https://discourse.slicer.org/t/ideal-hardware-configuration-for-high-quality-segmentations/9281 "2019-11-24T09:02:24Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![dzenanz](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/dzenanz/32/1992_2.png) [@dzenanz](https://discourse.slicer.org/u/dzenanz)\
**Post date:** [November 25, 2019, 9:29pm UTC](https://discourse.slicer.org/t/ideal-hardware-configuration-for-high-quality-segmentations/9281/17 "2019-11-25T21:29:54Z")

</div>

[This code](https://github.com/KitwareMedical/HASI/blob/fe38e0f08682fd3ba2fd9ec816118b844321fdb8/segmentBonesInMicroCT.cxx#L102-L155) is ready to be stolen. As `Maurer`, `Not` and `Threshold` filters are parallelized, this should scale with number of CPU cores, which is not the case with regular morphology. Not to mention that the size of radius mostly doesn’t matter for computation time.

---

_[View the full topic](https://discourse.slicer.org/t/ideal-hardware-configuration-for-high-quality-segmentations/9281)._
