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
We can either grab StartTime from the preprocessed BOLD file's sidecar or find the config.toml file from the fMRIPrep run and grab the config.workflow.slice_time_ref value.
Also, we might need to either patch in the selected reference as config.workflow.slice_time_ref or modify fmriprep.workflows.bold.stc.init_bold_stc_wf to accept the slice time reference as a parameter.
The text was updated successfully, but these errors were encountered:
If we want to support minimal derivatives, then we need to grab the slice_time_ref from the config file. However, I also think that limits the generalizability of the fMRIPost workflow. I think we want these fMRIPost workflows to theoretically work on any BIDS-compliant derivatives dataset with the right outputs, and the config file is a Nipreps-specific creation.
We can either grab
StartTime
from the preprocessed BOLD file's sidecar or find the config.toml file from the fMRIPrep run and grab theconfig.workflow.slice_time_ref
value.Also, we might need to either patch in the selected reference as
config.workflow.slice_time_ref
or modifyfmriprep.workflows.bold.stc.init_bold_stc_wf
to accept the slice time reference as a parameter.The text was updated successfully, but these errors were encountered: