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

Infer the slice timing reference from fMRIPrep derivatives #60

Open
tsalo opened this issue Sep 1, 2024 · 2 comments
Open

Infer the slice timing reference from fMRIPrep derivatives #60

tsalo opened this issue Sep 1, 2024 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@tsalo
Copy link
Collaborator

tsalo commented Sep 1, 2024

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.

@tsalo tsalo added the bug Something isn't working label Sep 1, 2024
@tsalo tsalo added this to the 24.0.0 milestone Sep 18, 2024
@tsalo
Copy link
Collaborator Author

tsalo commented Sep 25, 2024

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.

@effigies
Copy link
Member

If you're doing minimal derivatives, you need to run the STC yourself, so you can give end-users the choice or make it for them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants