# ERROR with DCE MRI loading in DICOM Browser

**URL:** <https://discourse.slicer.org/t/error-with-dce-mri-loading-in-dicom-browser/327>\
**Category:** Support\
**Created:** [May 16, 2017, 5:23pm UTC](https://discourse.slicer.org/t/error-with-dce-mri-loading-in-dicom-browser/327 "2017-05-16T17:23:54Z")\
**Posts on this page:** 1\
**Showing post:** 41

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [June 7, 2017, 3:30pm UTC](https://discourse.slicer.org/t/error-with-dce-mri-loading-in-dicom-browser/327/41 "2017-06-07T15:30:54Z")

</div>

We are moving forward with the implementation discussed in this thread: [Slicer DICOM Scalar volume plugin relies on (old) GDCM: why do we not use DCMTK?](https://discourse.slicer.org/t/slicer-dicom-scalar-volume-plugin-relies-on-old-gdcm-why-do-we-not-use-dcmtk/354/15)

We should hopefully have it in the application sometime soon. I will followup with @pieper later this week. I think fixing this problem of failing read of scalar volume in the Slicer application should be done no matter what.

---

_[View the full topic](https://discourse.slicer.org/t/error-with-dce-mri-loading-in-dicom-browser/327)._