You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to see added in this software?
If we want to be able to chain nipost workflows, we'll need to include the ability to ingest common targets, depending on the workflow. In this case, I'm thinking specifically about chaining ICA-AROMA and ME-ICA. Typically, I think we'd run ME-ICA after ICA-AROMA, since AROMA requires specific ICA settings (e.g., SUSAN-based smoothing, ICA in MNI152NLin6Asym-2mm space), but I do want to support the opposite organization, which would mean (1) ingesting ICA derivatives and (2) checking that they match what ICA-AROMA expects (at minimum checking the space and resolution).
Do you have any interest in helping implement the feature?
What would you like to see added in this software?
If we want to be able to chain nipost workflows, we'll need to include the ability to ingest common targets, depending on the workflow. In this case, I'm thinking specifically about chaining ICA-AROMA and ME-ICA. Typically, I think we'd run ME-ICA after ICA-AROMA, since AROMA requires specific ICA settings (e.g., SUSAN-based smoothing, ICA in MNI152NLin6Asym-2mm space), but I do want to support the opposite organization, which would mean (1) ingesting ICA derivatives and (2) checking that they match what ICA-AROMA expects (at minimum checking the space and resolution).
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
Related to ME-ICA/fmripost-tedana#5 and nipreps/fmripost-phase#5.
The text was updated successfully, but these errors were encountered: