# DICOM volume orientation may be bad

**URL:** <https://discourse.slicer.org/t/dicom-volume-orientation-may-be-bad/10068>\
**Category:** Support\
**Created:** [February 2, 2020, 10:15am UTC](https://discourse.slicer.org/t/dicom-volume-orientation-may-be-bad/10068 "2020-02-02T10:15:49Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [February 2, 2020, 7:04pm UTC](https://discourse.slicer.org/t/dicom-volume-orientation-may-be-bad/10068/5 "2020-02-02T19:04:45Z")

</div>

I’ve filed an ITK bug report: [https://github.com/InsightSoftwareConsortium/ITK/issues/1587](https://github.com/InsightSoftwareConsortium/ITK/issues/1587)

This minor ITK version upgrade has caused us so much headache already - build failures in all components that uses ITK (Slicer core, BRAINS, Elastix, etc.), DICOM errors ([1](https://github.com/InsightSoftwareConsortium/ITK/issues/1586), [2](https://github.com/InsightSoftwareConsortium/ITK/issues/1587)), SimpleITK failure on all operating systems with various reasons (Windows issue is fixed now but we still don’t have solution for the [MacOS error](https://discourse.slicer.org/t/sitkutils-pullvolumefromslicer-makes-slicer-crash/9781/8)), [lack of filter progress updates](https://discourse.itk.org/t/no-progress-reporting-in-itk5/2630), etc. The ITK team is very responsive but it is still quite frustrating that we need to spend so much time with investigating these regressions.

---

_[View the full topic](https://discourse.slicer.org/t/dicom-volume-orientation-may-be-bad/10068)._