derivatives=True fails silently if there is not dataset_description.json
See original GitHub issuesimilar to #169, but I believe the dataset_description.json
file is now required in derivatives.
I have a minimally reproducible example demonstrating the silent failure if dataset_description.json
is not included with the appropriate keys in the derivatives directory.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Derivatives indexing fails silently for deriv directories that lack ...
The problem is that if there's no dataset_description.json file in a folder, we can't simply assume the user made a mistake—it could be...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sorry, I mean the
bids-validator
Python package is tied to thebids-validator
Node package version. If they semantically version their Node packages to indicate spec version (e.g., bids-validator <2 => BIDS spec < 2), then we can safely set an upper bound.We should probably start versioning everything, and allow users to specify the version they want. But I think this should be locked to spec version changes (i.e., right now there’s no reason to want to use a broken version once it’s fixed).