# Issues reproducing N4BiasFieldCorrection results in Windows and Linux

**URL:** <https://discourse.itk.org/t/issues-reproducing-n4biasfieldcorrection-results-in-windows-and-linux/1623>\
**Category:** Engineering\
**Tags:** reproducibility, mri, neuroimaging, n4biasfield, linux\
**Created:** [February 25, 2019, 1:46pm UTC](https://discourse.itk.org/t/issues-reproducing-n4biasfieldcorrection-results-in-windows-and-linux/1623 "2019-02-25T13:46:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lassoan](https://discourse.itk.org/user_avatar/discourse.itk.org/lassoan/32/27_2.png) [@lassoan](https://discourse.itk.org/u/lassoan)\
**Post date:** [February 26, 2019, 2:51pm UTC](https://discourse.itk.org/t/issues-reproducing-n4biasfieldcorrection-results-in-windows-and-linux/1623/4 "2019-02-26T14:51:25Z")

</div>

> [@rcorredorj](#):
>
> thinking that every machine gives a different result is a bit shocking

This should not be shocking at all. Floating-point results are often somewhat different depending on what compiler, compiler options, and hardware you use.

You may force high-precision computation, which may make the results more consistent but increases computation time. If an algorithm is robust then these small numerical differences should cause negligible difference in the final output.

---

_[View the full topic](https://discourse.itk.org/t/issues-reproducing-n4biasfieldcorrection-results-in-windows-and-linux/1623)._
