Closed Aureleane closed 2 years ago
Hi Aureleane, can you describe in a bit more detail which registration you refer to and what application/executable you are using?
If you refer to niftymic_register_image, then this is on purpose. The temporary output is a resampled version of the SRR to the reference grid (e.g. template space). However, to prevent the resampling from affecting the image quality, a subsequent SRR step with updated transformations in reference space (e.g. template space) is recommended. See here for the follow-up steps.
Hello Renbem,
Thank you for your answer. I am indeed using niftymic_register_image, to register an SRR outcome (from niftymic_reconstruct_volume) to a template so it can have the same anatomical space. I am not sure I understand the subsequent SRR steps with the update transformations. Is it niftymic_reconstruct_volume_from_slices that has to be appplied to the output images of the registration?
Great, thanks. The first option worked.
Great. I'm glad to hear.
Hello,
I have started using Niftymic very recently, more precisely the registration. The output file given contains the transformation. The transformed image itself, which is the one I need, was a bit harder to find, as it is sent to the temporary files. I was wondering if it would be possible to implement a solution to choose in which file to send the registered image instead of the transformation.
Thanks !