Skip to content

Anatomical CompCor enhancement #1458

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

Open
rciric opened this issue Dec 20, 2018 · 2 comments
Open

Anatomical CompCor enhancement #1458

rciric opened this issue Dec 20, 2018 · 2 comments

Comments

@rciric
Copy link
Contributor

rciric commented Dec 20, 2018

  • Allow anatomical CompCor to operate separately in WM and CSF compartments (w_comp_cor and c_comp_cor according to BEP012 and RC1). Whereas the original approach described by Behzadi and colleagues (and currently used in fmriprep) uses a combined WM+CSF noise ROI for anatomical CompCor, aCompCor as deployed more recently by Muschelli and colleagues uses separate nuisance masks for WM and CSF. This latter approach was also used in recent benchmarking studies (1, 2).
  • Relatedly, some images may not have sufficient resolution for discrimination of separate WM and CSF masks. (For instance, much of the T2w rat data we’ve looked at has poorly discriminable CSF boundaries.) Thus, it would be helpful if the pipeline supported the option of using only the WM compartment when generating regressors.
  • To facilitate selection of an appropriate number of components for confound regression, save the eigenvalues/singular values for each component identified by CompCor approaches. Percentage of variance explained can either be saved directly in an additional metadata field (preferable) or computed from the singular values. The draft of BEP012 contained provisions for doing this; the most logical place for this would probably be in ~desc-confounds_regressors.json or ~decomposition.json.

I would be happy to help with any of these implementations that you think are worthwhile.

@oesteban
Copy link
Member

They are worthwhile indeed. Please go ahead :)

@oesteban
Copy link
Member

@rciric is this done? Please close if so or describe what's missing otherwise

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

No branches or pull requests

2 participants