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

EPInorm to replace EPI->T1w->MNI registration #620

Open
effigies opened this issue Jul 28, 2017 · 8 comments
Open

EPInorm to replace EPI->T1w->MNI registration #620

effigies opened this issue Jul 28, 2017 · 8 comments
Labels
effort: high Estimated high effort task feature impact: high Estimated high impact task refactoring

Comments

@effigies
Copy link
Member

http://onlinelibrary.wiley.com/doi/10.1002/hbm.23737/full

Supersedes #253, and may make ultimately replace SyN-based susceptibility distortion correction (#496/#544).

@chrisgorgo
Copy link
Contributor

When you have read the paper carefully could you list the pros, cons, and risks (things to look out for) of replacing syn based SDC with EPInorm?

@chrisgorgo
Copy link
Contributor

It might be also interesting to think about this in terms of a new optional target template EPIMNI.

@oesteban
Copy link
Member

That target would not be the same as MNI but specifying a resolution?

@chrisgorgo
Copy link
Contributor

The original paper used an EPI template instead of a T2w one (which we would have to use if we wanted to stick to 2009c) https://twitter.com/vdcalhoun/status/890217862010355713

@effigies
Copy link
Member Author

Looking at the EPI/T2 templates in SPM12, these at least are very similar; EPI.nii basically looks like a skull-stripped version of T2.nii. I haven't looked at the 2009c ones, but at a first pass, I'd think skull-stripping the T2w template and rescaling to match the EPI (as we do in creating the inverse T1w image) would get us to a similar starting point as EPInorm.

I'd think an EPIMNI target would just be the same as MNI... I'm not sure what you have in mind, unless it's to say don't bother resampling the anatomical to the MNI space. (Which, I'd think we wouldn't bother doing if we use EPInorm, unless we want to have a warp back to subject-native space.)

I feel like a major test of the (EPI -> MNI -> T1w) pipeline replacing SyN-SDC would be surface-sampling.

I'll give the paper a close reading and share my notes.

@chrisgorgo
Copy link
Contributor

I see - thanks for doing this comparison.

@chrisgorgo
Copy link
Contributor

@chrisgorgo
Copy link
Contributor

@oesteban oesteban added this to Watching in 1.3.0 Mar 1, 2018
@oesteban oesteban moved this from Watching to To do in 1.3.0 Jul 31, 2018
@oesteban oesteban moved this from To do to In progress in 1.3.0 Oct 18, 2018
@oesteban oesteban removed this from In progress in 1.3.0 Jan 12, 2019
@oesteban oesteban removed this from the 1.1.0 milestone Jan 30, 2019
@oesteban oesteban added this to To do in pipelines Mar 6, 2019
@oesteban oesteban added impact: high Estimated high impact task effort: high Estimated high effort task and removed potential hackathon project labels Mar 16, 2019
@franklin-feingold franklin-feingold moved this from To do to Issues B-list in pipelines May 6, 2019
@oesteban oesteban added this to the 2.0.0 milestone Jul 11, 2019
@effigies effigies moved this from Issues B-list to Issues A-list in pipelines Sep 30, 2019
@oesteban oesteban moved this from Issues A-list to Triage in pipelines May 7, 2020
@oesteban oesteban removed this from the 20.4.0 milestone May 28, 2020
@oesteban oesteban removed this from Triage in pipelines Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: high Estimated high effort task feature impact: high Estimated high impact task refactoring
Projects
None yet
Development

No branches or pull requests

3 participants