# RTStruct viewing anomalies for radiomics

**URL:** <https://discourse.slicer.org/t/rtstruct-viewing-anomalies-for-radiomics/16512>\
**Category:** Support\
**Created:** [March 12, 2021, 10:15pm UTC](https://discourse.slicer.org/t/rtstruct-viewing-anomalies-for-radiomics/16512 "2021-03-12T22:15:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![furMan](https://avatars.discourse-cdn.com/v4/letter/f/ea666f/32.png) [@furMan](https://discourse.slicer.org/u/furMan)\
**Post date:** [March 12, 2021, 10:15pm UTC](https://discourse.slicer.org/t/rtstruct-viewing-anomalies-for-radiomics/16512/1 "2021-03-12T22:15:25Z")

</div>

Operating system:Windows 10  
Slicer version: 4.10.2  
Expected behavior: imported RTStruct mask to show what MRI image regions are masked, and non-masked, when viewing  
Actual behavior: Two problems:(1) The displayed binary image mask has artifacts (some masked slices are not shown as masked) (2) when I mouse over the mask + image, the ROI does not always show as being masked.

Basically, the masking when using the RTStruct Dicom doesn’t seem reliable when viewing. This is not a problem when I use a binary mask read in as a Dicom volume.

If this is just a viewing artifact, I’m not concerned. My concern is whether the RTstruct masks are not reliable for radiomics processing.

Thank you,  
Mike

---

<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:** [March 13, 2021, 2:14pm UTC](https://discourse.slicer.org/t/rtstruct-viewing-anomalies-for-radiomics/16512/2 "2021-03-13T14:14:47Z")

</div>

If you view the closed surface representation in slice views and you have complex segmentation (with holes, etc) then it is indeed just a visualization artifact. You can either switch to binary labelmap representation or switch to a recent Slicer version, where this problem has been already fixed.