# Mrtrix 3.0.3 import broken, 3.0.2 fine?

**URL:** <https://community.mrtrix.org/t/mrtrix-3-0-3-import-broken-3-0-2-fine/5614>\
**Category:** Uncategorized\
**Created:** [March 18, 2022, 11:08pm UTC](https://community.mrtrix.org/t/mrtrix-3-0-3-import-broken-3-0-2-fine/5614 "2022-03-18T23:08:16Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jdtournier](https://community.mrtrix.org/user_avatar/community.mrtrix.org/jdtournier/32/2594_2.png) [@jdtournier](https://community.mrtrix.org/u/jdtournier)\
**Post date:** [March 19, 2022, 10:27am UTC](https://community.mrtrix.org/t/mrtrix-3-0-3-import-broken-3-0-2-fine/5614/4 "2022-03-19T10:27:32Z")

</div>

Ah, yes, that’s not right. It looks like [this issue](https://community.mrtrix.org/t/problem-with-sorting-of-dicom-images-using-mrconvert/5493), recently reported also for Phillips data. If that’s the case, the fix is just waiting to merge as part of the pull request I linked to above. If you’re happy to share the data with me, I can take a look.

What I hadn’t realised was that this wasn’t an issue with 3.0.2 – I’ll look into what changed between the two versions to figure out what we did differently. I have a battery of test data that I use to verify that everything works as expected when I make changes to the DICOM handling, so I’m surprised I wouldn’t have picked this up if there had been such an obvious a regression… 😬

---

_[View the full topic](https://community.mrtrix.org/t/mrtrix-3-0-3-import-broken-3-0-2-fine/5614)._