# TotalSegmentor python package for Slicer plugin showing error

**URL:** <https://discourse.slicer.org/t/totalsegmentor-python-package-for-slicer-plugin-showing-error/35259>\
**Category:** Support\
**Tags:** totalsegmentator\
**Created:** [April 3, 2024, 3:45pm UTC](https://discourse.slicer.org/t/totalsegmentor-python-package-for-slicer-plugin-showing-error/35259 "2024-04-03T15:45:26Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [April 5, 2024, 11:24am UTC](https://discourse.slicer.org/t/totalsegmentor-python-package-for-slicer-plugin-showing-error/35259/4 "2024-04-05T11:24:25Z")

</div>

I looked up about MSD and it seems that heart data is MRI while TotalSegmentator works only on CT images. The developer of TotalSegmentator has mentioned about creating an MRI version, but there is no timeline about when it would be available to use.

Other groups are also aiming to build an MRI based segmentator, but again nothing publicly available at this moment.

> [@TotalSegmentator for MRI dataset](https://discourse.slicer.org/t/totalsegmentator-for-mri-dataset/35080/3):
>
> We have a project underway to try training an MR segmenter based on TotalSegmentator using the SynthSeg approach (not muscles yet though). The preprint paper actually just went up on arxiv: Would be great to generalize to other segmentation tasks.

---

_[View the full topic](https://discourse.slicer.org/t/totalsegmentor-python-package-for-slicer-plugin-showing-error/35259)._