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

Support minimal derivatives from fMRIPrep #12

Open
tsalo opened this issue Dec 6, 2023 · 5 comments
Open

Support minimal derivatives from fMRIPrep #12

tsalo opened this issue Dec 6, 2023 · 5 comments
Labels
enhancement New feature or request

Comments

@tsalo
Copy link
Collaborator

tsalo commented Dec 6, 2023

What would you like to see added in this software?

This came up in today's NiPreps roundup call. I initially assumed that the fMRIPost workflow would use standard-space derivatives from fMRIPrep. However, what would be better would be for the fMRIPost Apps to have workflows that apply transforms from the minimal fMRIPrep outputs.

Do you have any interest in helping implement the feature?

Yes

Additional information / screenshots

No response

@tsalo tsalo added the enhancement New feature or request label Dec 6, 2023
@tsalo
Copy link
Collaborator Author

tsalo commented Feb 16, 2024

If we use minimal derivatives, then we also need access to the raw dataset as well, right?

@effigies
Copy link
Member

Yes.

@tsalo
Copy link
Collaborator Author

tsalo commented Feb 18, 2024

Since derivatives datasets can also be self-contained datasets, I think providing just derivatives (assuming they were run with "full" mode) should be allowed as well. Not sure how well all of that would play with the BIDS execution spec though.

@effigies
Copy link
Member

Yeah, that should be doable. Look for space-... And only look up the bits to recalculate it if needed.

@tsalo tsalo mentioned this issue May 13, 2024
@tsalo
Copy link
Collaborator Author

tsalo commented May 15, 2024

With minimal mode, there won't be a confounds timeseries file, so in that case:

  1. --dummy-scans needs to be required.
  2. Motion parameters need to be extracted from the motion correction transform file.

@tsalo tsalo mentioned this issue Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants