# Elastics Step 2.command "elsatix return to non-zero exit status 1 error"

**URL:** <https://discourse.slicer.org/t/elastics-step-2-command-elsatix-return-to-non-zero-exit-status-1-error/39611>\
**Category:** Support\
**Tags:** registration\
**Created:** [October 9, 2024, 12:52pm UTC](https://discourse.slicer.org/t/elastics-step-2-command-elsatix-return-to-non-zero-exit-status-1-error/39611 "2024-10-09T12:52:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [October 10, 2024, 4:20am UTC](https://discourse.slicer.org/t/elastics-step-2-command-elsatix-return-to-non-zero-exit-status-1-error/39611/2 "2024-10-10T04:20:36Z")

</div>

Do you get any error if you try to register a `MRBrainTumor1` and `MRBrainTumor2` sample data sets to each other using `Elastix` module?

If it works then it is not a problem with Elastix but with the bone segmentation extension. Check out this topic:

> [@ABL Temporal Bone Segmentation Module ERROR](https://discourse.slicer.org/t/abl-temporal-bone-segmentation-module-error/39609/2):
>
> This means the fixed and moving images are too far from each other. Most likely the issue is that you do not register your image to the atlas correctly. A few people has struggled with this, too - see [here](https://github.com/Auditory-Biophysics-Lab/Slicer-ABLTemporalBoneSegmentation/issues/9). You may work with these people to figure out how to do this registration. You may try to contact the developers of this extension, but there have not been any updates in the repository for several years, so you may need to do some digging to find someone.

---

_[View the full topic](https://discourse.slicer.org/t/elastics-step-2-command-elsatix-return-to-non-zero-exit-status-1-error/39611)._