# CT vs MRI reading

**URL:** https://discourse.vtk.org/t/ct-vs-mri-reading/2095
**Category:** Support
**Tags:** file-formats
**Created:** [November 14, 2019, 9:39am UTC](https://discourse.vtk.org/t/ct-vs-mri-reading/2095 "2019-11-14T09:39:39Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![flaviu2](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/f/74df32/32.png) [@flaviu2](https://discourse.vtk.org/u/flaviu2)
#### Post date: [November 14, 2019, 9:39am UTC](https://discourse.vtk.org/t/ct-vs-mri-reading/2095/1 "2019-11-14T09:39:39Z")

</div>

Is there any difference between read DICOM **CT** data or DICOM **MRI** data ? I have written code that read DICOM data and represent it as vtkVolume. I used DICOM VTK library for that ([https://github.com/dgobbi/vtk-dicom](https://github.com/dgobbi/vtk-dicom)) (_BTW, excellent library_), and goes well, and volume look well. But if I load a **MRI** dicom data, volume looks unclear somehow … and I wonder what could be the difference ? From your experience, is there any difference between how to read a **CT** or a **MRI**? Because I don’t see another approach to build a volume from input data …