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

Track sources with DatasetLinks and BIDS-URIs #3252

Closed
tsalo opened this issue Mar 9, 2024 · 4 comments · Fixed by #3255 or #3297
Closed

Track sources with DatasetLinks and BIDS-URIs #3252

tsalo opened this issue Mar 9, 2024 · 4 comments · Fixed by #3255 or #3297

Comments

@tsalo
Copy link
Collaborator

tsalo commented Mar 9, 2024

What would you like to see added in fMRIPrep?

I was thinking it would be nice to output Sources metadata fields for all outputs, using DatasetLinks and BIDS URIs to track the files.

DatasetLinks and BIDS URIs were added in 1.8.0, so we would need to increase the BIDSVersion to at least 1.8.0.

Do you have any interest in helping implement the feature?

Yes

Additional information / screenshots

I've had some success doing this in XCP-D, and I think it would be even easier in fMRIPrep since we could put a DatasetLinks field in the Config object.

effigies pushed a commit that referenced this issue Mar 22, 2024
Closes #3252. This is just a first pass- it only modifies the RawSources
for now. I can add the immediate Sources in another PR (this'll require
a lot more effort).

## Changes proposed in this pull request

- Add `DatasetLinks` field to the `dataset_description.json`
    - The input dataset is called `raw`
- Any other datasets supplied through `--derivatives` are automatically
named `deriv-<index>`. We might want to support named derivatives at
some point.
- Replace BIDS-relative paths in `RawSources` fields with BIDS-URIs.
- Change `RawSources` to `Sources` in the sidecar files, since
`RawSources` is deprecated.

## Documentation that should be reviewed

I'll probably need to update the documentation, but haven't yet.

---------

Co-authored-by: Mathias Goncalves <goncalves.mathias@gmail.com>
@effigies
Copy link
Member

effigies commented Jun 4, 2024

@tsalo Could you redo #3255 with the latest changes in #3292 merged into master? I didn't want to try to do it in a merge commit.

@effigies effigies reopened this Jun 4, 2024
@tsalo
Copy link
Collaborator Author

tsalo commented Jun 4, 2024

Sorry, I'm a little confused. It doesn't look like the changes in #3255 were reverted in master when you merged in #3292. Am I missing something?

@effigies
Copy link
Member

effigies commented Jun 4, 2024

The ds_boldmask_wf workflow that got pulled out in maint/23.2.x still has RawSources. When I merged the latest release into master (2e863b7), I did not try to merge it as if you had split the workflow out from the current state of master.

@tsalo
Copy link
Collaborator Author

tsalo commented Jun 4, 2024

Ohhh okay. I'll take a look at that then.

effigies pushed a commit that referenced this issue Jun 4, 2024
Closes #3252.

## Changes proposed in this pull request

- Replace `RawSources` in `init_ds_boldmask_wf` with `Sources`
determined using `BIDSURI`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants