Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

output in native/original space #1376

Open
a3sha2 opened this Issue Nov 9, 2018 · 5 comments

Comments

Projects
5 participants
@a3sha2
Copy link

a3sha2 commented Nov 9, 2018

is there anyway to specify EPI output in native/orig space?

@a3sha2 a3sha2 changed the title output_space in native/original space output in native/original space Nov 9, 2018

@effigies

This comment has been minimized.

Copy link
Collaborator

effigies commented Nov 9, 2018

You mean corrected to each BOLD series' reference BOLD image, rather than aligned to the T1w image? Or would they be aligned to some subject-level mean BOLD?

@a3sha2

This comment has been minimized.

Copy link
Author

a3sha2 commented Nov 9, 2018

yes, exactly

@effigies

This comment has been minimized.

Copy link
Collaborator

effigies commented Nov 9, 2018

We don't currently support that, but it shouldn't be too hard to enable. Do you have any interest in submitting a pull request? We can orient you to the code and guide you through the process.

@chrisfilo

This comment has been minimized.

Copy link
Contributor

chrisfilo commented Nov 9, 2018

I would love to learn more about the motivation for such a feature.

@oesteban oesteban added this to To do in pipelines Mar 6, 2019

@jooh

This comment has been minimized.

Copy link

jooh commented Mar 7, 2019

@chrisfilo the main motivation would be reuse of ROIs that are provided with BIDS-format datasets. It is fairly common to save ROI masks in native EPI space. That's what you see in e.g. ds000232 and ds001246.

This follows from the standard SPM pipeline, where coregistration is conventionally done by updating the affine in the header, and then only applied to the image data during normalisation to the MNI template. So if you use SPM-derived routines like this one to construct ROIs you will end up with EPI-space ROI files, if your SPM model ran without normalisation.

Also, perhaps I'm a masochist but I actually like drawing my functional ROIs with native-EPI activations overlaid on the mean EPI so I can see what the image intensities look like... If you do this in fslview or mrTools you will end up with native EPI ROI masks.

It's not difficult to reslice the ROI mask, but you won't get the exact same voxels due to interpolation. And this seems an unnecessary imprecision.

Finally to clarify, @effigies, I don't know that you'd want these outputs aligned only to subject-mean BOLD. I think you would want to reproduce SPM behaviour, so the image data remains in EPI native space but have the updated header affine that brings them in registration with the native T1. This way you can still overlay anatomicals and functionals in sensible viewers (ie not fslview).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.