# Running Elastix registration changes save location of "fixed" and "moving" volumes
**URL:** https://discourse.slicer.org/t/running-elastix-registration-changes-save-location-of-fixed-and-moving-volumes/8093
**Category:** Development
**Created:** [August 19, 2019, 4:25pm UTC](https://discourse.slicer.org/t/running-elastix-registration-changes-save-location-of-fixed-and-moving-volumes/8093 "2019-08-19T16:25:26Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@hbraunDSP](https://discourse.slicer.org/u/hbraunDSP)
#### Post date: [August 19, 2019, 4:25pm UTC](https://discourse.slicer.org/t/running-elastix-registration-changes-save-location-of-fixed-and-moving-volumes/8093/1 "2019-08-19T16:25:27Z")
Hi everyone,
I’ve been using the Elastix extension for some registrations, and it’s been working great. However, after running Elastix the volumes I selected for the “fixed” and “moving” volumes are by default saved as metaImage (`*.mha`) files in the `[home]/AppData/Local/Temp/Slicer/Elastix/[datetime]/input/` directory. This behavior is unexpected and annoying: my data and slicer scene files are stored on a network drive in Nifti format, and I want to keep it that way. The `...elastix/.../input/` directory is on my local machine, as it should be for speed. If I forget to change the volumes back to the original location, the MRML scene is broken when opening from any computer other than the one used to run the registration. On top of this, I don’t want to just overwrite the original Nifti files in case Slicer changed something (e.g. losing track of header data), so I have to re-add the files after completing registration.
Is this behavior necessary for some reason I haven’t thought of? Should I open an issue on [https://github.com/lassoan/SlicerElastix/issues](https://github.com/lassoan/SlicerElastix/issues) ? Is there a way to tell Slicer to keep the original image locations?
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [August 21, 2019, 4:40pm UTC](https://discourse.slicer.org/t/running-elastix-registration-changes-save-location-of-fixed-and-moving-volumes/8093/2 "2019-08-21T16:40:10Z")
Good point, we should indeed not change the default save location (it is an unintended side effect). Please enter a bug report in SlicerElastix issue tracker.