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.

Sign up for GitHub

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

Jump to bottom

Track immediate Sources when possible #69

Open
tsalo opened this issue Aug 20, 2024 · 1 comment
Open

Track immediate Sources when possible #69

tsalo opened this issue Aug 20, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@tsalo
Copy link
Member

tsalo commented Aug 20, 2024 •
edited
Loading

Summary

I want to start tracking source data for output files.

Similar to nipreps/fmriprep#3261.

Next Steps

  1. Add DatasetLinks to dataset_description.json files for all of the QSIRecon derivative datasets.
  2. Start passing along metadata between nodes in the reconstruction workflows to track the origin of each output file.
  3. Add a step to build BIDS-URIs from the source files.
  4. Add the source file metadata to the DerivativesDataSinks writing out the derivative files.
@tsalo tsalo added the enhancement New feature or request label Aug 20, 2024
This was referenced Aug 20, 2024
Merged
Merged
@tsalo
Copy link
Member Author

tsalo commented Aug 23, 2024 •
edited
Loading

One thing that will help with this is to use the output file from DerivativesDataSinks as the input to further workflows, when possible.

@tsalo tsalo mentioned this issue Aug 24, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tsalo