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

longitudinal option for T1 processes #9

Open
cbedetti opened this issue Sep 9, 2019 · 3 comments
Open

longitudinal option for T1 processes #9

cbedetti opened this issue Sep 9, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@cbedetti
Copy link

cbedetti commented Sep 9, 2019

Would it be possible to add an optional step after the N4 T1 process to create an unbiased intra-subject template ?

fmriprep is doing already this step with mri_robust_template from freesurfer.

I could work on this feature if you think tractoflow should have it.

Issues I could see :

  • it adds a freesurfer dependency
  • maybe a solution exists with ANTs but I'm not familiar with this software.
@arnaudbore
Copy link
Contributor

@cbedetti
Copy link
Author

cbedetti commented Sep 9, 2019

I was thinking only for T1 but a multivariate version seems even better.

The template construction process should be done just before Resample DWI and Resample T1, right ?

But at this stage of the pipeline :

  • T1s are not yet brain extracted or cropped
  • DTI metrics are not produced

So the Resample T1 process should be delayed and temporary DTI metrics should be computed after the Normalize DWI process.

Is that right ?

@jchoude
Copy link
Member

jchoude commented Sep 9, 2019

  1. I don't think we need the multivariate in the sense of using DTI metrics as well. @frheault has experience in building templates of T1s.

  2. What would be the goal, here? How would it influence the rest of the pipeline?

My main concern is that this is quite a long process, and would potentially (depending on which step is planned to use that template) block multiple other processes, which we normally avoid as much as possible.

Depending on the goal of the template building step, it might better be suited as a separate workflow. Our (well, at least mine) philosophy is that writing separate workflows for tasks that do not directly impact the dMRI processing steps is often better, since it allows to better distribute compute resources, etc.

@arnaudbore arnaudbore added the enhancement New feature or request label Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants