# Cardiac MRI loading erros

**URL:** <https://discourse.slicer.org/t/cardiac-mri-loading-erros/19926>\
**Category:** Support\
**Tags:** segmentation\
**Created:** [September 30, 2021, 9:36am UTC](https://discourse.slicer.org/t/cardiac-mri-loading-erros/19926 "2021-09-30T09:36:20Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [October 7, 2021, 4:38am UTC](https://discourse.slicer.org/t/cardiac-mri-loading-erros/19926/7 "2021-10-07T04:38:39Z")

</div>

I’ve checked the sample images that were shared in [this post](https://discourse.slicer.org/t/blood-flow-simulation-from-cardiac-cine-mri/20036/3).

You can load them by enabling “Advanced” mode and selecting the “… Volume Sequence…” loadables:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/7/2/72054273e557919da24158cf2a9bf605f4495886.png)

Most of the datasets are 4D data sets (3D+t), although most of them just 3-5 slice thick slab (except series 601, which is a bit thicker, as it contains 18 slices). There are also a few flow data sets, which contain 3 sub-sequences (PCA, FFE, and VELOCITY MAP).

I’ve submitted a [pull request](https://github.com/fedorov/MultiVolumeImporter/pull/49) to the multi-volume importer module, which will change the default behavior so that you will not need to use the advanced mode to load your sequences as thick slabs. It will probably take just a few days to get integrated into the Slicer Preview Release.

---

_[View the full topic](https://discourse.slicer.org/t/cardiac-mri-loading-erros/19926)._