-
Notifications
You must be signed in to change notification settings - Fork 111
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
qMRI JSON not allowed in root of dataset #1438
Comments
Any news on this? Can I help in any way? |
it's possible that all that's needed is an edit of https://github.com/bids-standard/bids-validator/blob/master/bids-validator/bids_validator/rules/top_level_rules.json -- so I think if you are keen, you could look into that? |
Thanks that helps as a pointer as to where to start! Will look into it but writing regular expression for qMRI files defo sounds fun... #KMN Should be tweak the bids example so that we have sort of test for this? |
Yup |
Noticed on one of my own dataset but tried the following on the bids example repo to demonstrate
tree qmri_mp2rage qmri_mp2rage ├── dataset_description.json ├── derivatives ├── inv-1_MP2RAGE.json # <---- this should be valid, no? ├── README └── sub-1 └── anat ├── sub-1_inv-1_MP2RAGE.json ├── sub-1_inv-1_part-mag_MP2RAGE.nii ├── sub-1_inv-1_part-phase_MP2RAGE.nii ├── sub-1_inv-2_MP2RAGE.json ├── sub-1_inv-2_part-mag_MP2RAGE.nii ├── sub-1_inv-2_part-phase_MP2RAGE.nii └── sub-1_mod-MP2RAGE_defacemask.nii.gz
Was getting a similar error for
UNIT1.json
in the root folder of the dataset. I have not checked other qMRI related suffixes.@agahkarakuzu Can you cross check if you have time?
The text was updated successfully, but these errors were encountered: