# N4ITK MRI Bias Field Correction input file type?

**URL:** <https://discourse.slicer.org/t/n4itk-mri-bias-field-correction-input-file-type/13008>\
**Category:** Support\
**Created:** [August 15, 2020, 2:08am UTC](https://discourse.slicer.org/t/n4itk-mri-bias-field-correction-input-file-type/13008 "2020-08-15T02:08:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sgonzalez122](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@sgonzalez122](https://discourse.slicer.org/u/sgonzalez122)\
**Post date:** [August 15, 2020, 2:08am UTC](https://discourse.slicer.org/t/n4itk-mri-bias-field-correction-input-file-type/13008/1 "2020-08-15T02:08:27Z")

</div>

Operating system: macOS Catalina  
Slicer version: none  
Expected behavior: Output a volume in Nifti format  
Actual behavior: none

Hi there, I am new to 3D slicer and was wondering if it’s N4ITK Bias Field Correction module accepted Nifti image files as input. More specifically I plan to run this module on a T1 weighted MPRAGE brain volume in Nifti file format. I was wondering if the module with accept this format and also output a corrected volume in Nifti as well. Additionally, I was wondering if the Bias Field Image output is also output as a volume and what file type is output when using this option.

Thank you for your help,  
Stephen

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 15, 2020, 2:09am UTC](https://discourse.slicer.org/t/n4itk-mri-bias-field-correction-input-file-type/13008/2 "2020-08-15T02:09:24Z")

</div>

Yes, Slicer can read MRI from a Nifti file, apply bias correction, and save result as Nifti file.

---

<div class="post-metadata">

**Author:** ![sgonzalez122](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@sgonzalez122](https://discourse.slicer.org/u/sgonzalez122)\
**Post date:** [August 16, 2020, 8:12pm UTC](https://discourse.slicer.org/t/n4itk-mri-bias-field-correction-input-file-type/13008/3 "2020-08-16T20:12:09Z")

</div>

Thank you so much 🙂  
I was able to run it successfully, via command line, generate the bias field, and view it in FSL. It looks wonderful.

 ![1](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/0/7/0704bf956c8bb1157c9ee0cda5e4006dde531f04.png) ![2](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/d/4/d4ba98aac6e20498b67bf0e0b2b4654ac02cfbe0.png) ![3](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/f/c/fc62a25ce873ffbd9febd3e30ce093f7e22dbc93.png)

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 16, 2020, 9:21pm UTC](https://discourse.slicer.org/t/n4itk-mri-bias-field-correction-input-file-type/13008/4 "2020-08-16T21:21:22Z")

</div>

Great! Check out Slicer’s visualization and processing capabilities, too. We also have a FreeSurfer extension that can import data sets. There are tons of tools that fsleyes does not have - from virtual reality tractography to real-time surgical navigation with BrainLab/StealthStation/custom tracker, advanced image segmentation and surface editing, cutting, etc.