Skip to content

Conversation

effigies
Copy link
Contributor

This branch implements examples according to bids-standard/bids-specification#1714 (rendered: https://bids-specification--1714.org.readthedocs.build/en/1714/).

Please make PRs against the bep038 branch, and we will merge this PR as a part of merging BEP038.

@effigies
Copy link
Contributor Author

@oesteban Notes on atlas-suit:

  • atlas-*_description.json does not currently have a file rule. From reading the BEP, it looks like it can occur at any level of the hierarchy, which is not possible with the current structure of file rules. Is it problematic to require it to be found at the dataset root?
  • *_dseg.tsv need to be non-empty files.
  • *_stat-confidence_* - The stat entity is not defined.

Otherwise, this needs very little adjustment to the validator.

@oesteban
Copy link

  • atlas-*_description.json does not currently have a file rule. From reading the BEP, it looks like it can occur at any level of the hierarchy, which is not possible with the current structure of file rules. Is it problematic to require it to be found at the dataset root?

I don't think this should be a problem.

  • *_dseg.tsv need to be non-empty files.

Gotcha, will give them content.

  • *_stat-confidence_* - The stat entity is not defined.

desc then?

@effigies
Copy link
Contributor Author

  • *_stat-confidence_* - The stat entity is not defined.

desc then?

Sounds good to me.

@CPernet
Copy link
Contributor

CPernet commented Aug 18, 2025

I have added an example for an atlas we made, and want to distribute - this is thus a dataset. I think this is correct ?? I can see some redundancy between the dataset_description.json and the atlas-ONPNeuroMarkflorbetapir_description.json what do you guys think? @oesteban @effigies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants