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
Is your feature request related to a problem? Please describe.
While I'm a huge fan and in support of fMRIPrep, there are reasons not to use it. Working with a few datasets that unfortunately fell under this category, I was wondering howe NiBetaSeries could also be utilized without fMRIPrep outputs.
Describe the solution you'd like
I think a support for a myriad preprocessing pipelines is not possible and feasible. However, maybe 1 or 2 could be added (as long as they comply with BIDS).
Describe alternatives you've considered
More realistically, the docs could contain a respective primer and/or example that utilizes NiBetaSeries with a preprocessing pipeline other than fMRIPrep. Maybe something along the lines of the tutorial.
How do folks think about this?
The text was updated successfully, but these errors were encountered:
I am very open to making nibetaseries more adaptable to other preprocessing pipelines, NiBetaSeries is not dependent on fmriprep per se, but it is the the one I know most about. As long as the preprocessing pipeline fulfills the current state of the bids-derivatives specification, nibetaseries should be able to accommodate.
Is there a preprocessing pipeline you can share some example outputs for (and/or a link to the pipeline code) so we can develop a tutorial/tests to make sure it works?
Thx for the fast response @jdkent! You're of course right in that NiBetaSeriesshould also work with other preprocessing pipelines given the requirements you mentioned. I was more referring to the arguments that are rather fMRIPrep specific (e.g. confounds, etc.).
Re preprocessing pipelines: we could check the nipype examples, now living in niflows. However, they are not compliant with the derivatives specifications, hence would create a bit of work us (basically changing the datasink of the examples). One that is compliant would be fmriflows (disclaimer: I'm helping out in that project.). Both could be applied to the same dataset as used in the tutorial.
Is your feature request related to a problem? Please describe.
While I'm a huge fan and in support of fMRIPrep, there are reasons not to use it. Working with a few datasets that unfortunately fell under this category, I was wondering howe
NiBetaSeries
could also be utilized withoutfMRIPrep
outputs.Describe the solution you'd like
I think a support for a myriad preprocessing pipelines is not possible and feasible. However, maybe 1 or 2 could be added (as long as they comply with
BIDS
).Describe alternatives you've considered
More realistically, the docs could contain a respective primer and/or example that utilizes
NiBetaSeries
with a preprocessing pipeline other thanfMRIPrep
. Maybe something along the lines of the tutorial.How do folks think about this?
The text was updated successfully, but these errors were encountered: