# Mrconvert warning with aform and sform

**URL:** <https://community.mrtrix.org/t/mrconvert-warning-with-aform-and-sform/6008>\
**Category:** Uncategorized\
**Tags:** error\
**Created:** [September 5, 2022, 3:35am UTC](https://community.mrtrix.org/t/mrconvert-warning-with-aform-and-sform/6008 "2022-09-05T03:35:34Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [September 5, 2022, 8:32pm UTC](https://community.mrtrix.org/t/mrconvert-warning-with-aform-and-sform/6008/3 "2022-09-05T20:32:00Z")

</div>

> [@CarlisleYun79](#):
>
> I think that warning is serious problem for pre-process diffusion image.

Not necessarily, it could just be a very subtle mismatch due to machine precision – see [this thread](https://community.mrtrix.org/t/inconsistent-qform-sform-on-nifti-image/1663) for details.

However, if there is a genuine mismatch, it might be worth chasing down where this mismatch originates, and which of the sform or qform is to be trusted…

> [@CarlisleYun79](#):
>
> Is that right to input the json file on .mif file for dwifslprerpoc?

If you have it, yes – though that has no influence on the warning you get. It just means that any additional information present in the JSON will also be injected into the header of the `mif` file. You’ll basically end up with a single `mif` file that contains all the voxel data, the bvecs/bvals, and any other information present in the JSON. 👍

---

_[View the full topic](https://community.mrtrix.org/t/mrconvert-warning-with-aform-and-sform/6008)._