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

Make MNI space projection and ROI based analysis default for ANTs: Ofer #6

Open
tashrifbillah opened this issue Jul 29, 2019 · 0 comments
Labels

Comments

@tashrifbillah
Copy link
Contributor

The request has not been agreed upon.

  1. When running —StudyTemplate, currently the output will be in the original space coordinates (e.g., if 2X2X2, the output would be registered 2X2X2, and 2X2X2 skeleton). A better option would be that the output is in MNI space. I think that this can be achieved by setting the -template flag? (e.g, setting it to the FA image provided by FSL, or the one provided by ENIGMA?)

Correction: This is achieved by --space flag.

but I think registration to MNI should be the default option when using the StudyTemplate option. ... I think it would be better if an option could be set to NOT register to MNI (which will be evoked when using animal data for example).

I have reviewed my work flow. An "if" condition after this line can do the job. Shall I do it?

args.space=` pjoin(fslDataDir, 'standard', 'FMRIB58_FA_1mm.nii.gz')

Please double check the above template defines MNI space you referred to.

The code should also generate the ROI values for the regions in the MNI space by default.

Are we sure we want to do this? Because it will take time to do ROI based analysis. Again, it can be done with an if condition setting:

args.lut = pjoin(enigmaDir, 'ENIGMA_look_up_table.txt')
args.labelMap = pjoin(fslDataDir, 'atlases', 'JHU', 'JHU-ICBM-labels-1mm.nii.gz')

Again, do we want ROI based analysis based on using the the above LUT and ATLAS?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant