# Cranial and caudal directions are opposite when loading sequence of DICOM images

**URL:** <https://discourse.slicer.org/t/cranial-and-caudal-directions-are-opposite-when-loading-sequence-of-dicom-images/17428>\
**Category:** Support\
**Tags:** dicom\
**Created:** [May 4, 2021, 1:43am UTC](https://discourse.slicer.org/t/cranial-and-caudal-directions-are-opposite-when-loading-sequence-of-dicom-images/17428 "2021-05-04T01:43:23Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [May 10, 2021, 12:00pm UTC](https://discourse.slicer.org/t/cranial-and-caudal-directions-are-opposite-when-loading-sequence-of-dicom-images/17428/22 "2021-05-10T12:00:25Z")

</div>

Each of the steps you listed makes complete sense to me. After many such queries I think it is high time we detect DICOM loading and only allow it via the browser. Also it would be great simplifying the vtkITKArchetypeImageSeriesReader adjacent code.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 10, 2021, 12:34pm UTC](https://discourse.slicer.org/t/cranial-and-caudal-directions-are-opposite-when-loading-sequence-of-dicom-images/17428/23 "2021-05-10T12:34:19Z")

</div>

> [@lassoan](#):
>
> Probably merge all subclasses (vtkITKArchetypeDiffusionTensorImageReaderFile, vtkITKArchetypeImageSeriesReader, vtkITKArchetypeImageSeriesScalarReader, vtkITKArchetypeImageSeriesVectorReaderFile, vtkITKArchetypeImageSeriesVectorReaderSeries)

One historical note: a lot of the logic in these classes is split out because all the template instantiations led to memory issue in old compilers.

---

<div class="post-metadata">

**Author:** ![xackey](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/xackey/32/10860_2.png) [@xackey](https://discourse.slicer.org/u/xackey)\
**Post date:** [July 9, 2021, 11:00pm UTC](https://discourse.slicer.org/t/cranial-and-caudal-directions-are-opposite-when-loading-sequence-of-dicom-images/17428/24 "2021-07-09T23:00:33Z")

</div>

Hi.  
The issue has not been fixed yet in the latest 3D slicer (4.13.0).  
Could you tell me the current status?  
Thank you for your help.

---

<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:** [July 10, 2021, 1:44am UTC](https://discourse.slicer.org/t/cranial-and-caudal-directions-are-opposite-when-loading-sequence-of-dicom-images/17428/25 "2021-07-10T01:44:16Z")

</div>

DICOM loading using the Load Data Dialog (which is typically used for loading all other files in Slicer) is planned to be disabled. See [Disable DICOM import from "Add data" dialog · Issue #5726 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/issues/5726).

You should load DICOM data using the DICOM module. See more details at [Data Loading and Saving — 3D Slicer documentation](https://slicer.readthedocs.io/en/latest/user_guide/data_loading_and_saving.html#data-loading-and-saving).

[Previous page](https://discourse.slicer.org/t/cranial-and-caudal-directions-are-opposite-when-loading-sequence-of-dicom-images/17428.md?page=1)