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 provenance of derivatives #568

Closed
wants to merge 8 commits into from
Closed

Conversation

tsalo
Copy link
Member

@tsalo tsalo commented Oct 11, 2022

Closes #548.

To do:

  • Load metadata from the source BOLD file, and pass it along to derivatives.
  • Filter metadata dictionaries based on the needs of the specific derivative.
    • For example, ALFF and ReHo maps shouldn't have the RepetitionTime field.
  • Add extra fields as necessary.
    • For example, the SpatialReference field is required for fsLR data, AFAICT.
  • Identify any files feeding into each derivative.
    • The obvious one is the BOLD file, but there are probably others (e.g., confounds files for denoised data).

Changes proposed in this pull request

  • Update utils.bids.write_dataset_description to define a DatasetLinks field, if necessary, and add the preprocessed data path to it.

Documentation that should be reviewed

@tsalo tsalo added the enhancement New feature or request label Oct 12, 2022
@tsalo
Copy link
Member Author

tsalo commented Oct 18, 2023

Closing in favor of #966.

@tsalo tsalo closed this Oct 18, 2023
@tsalo tsalo deleted the file-provenance branch March 20, 2024 12:40
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

Successfully merging this pull request may close these issues.

Track provenance of derived files
1 participant