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

Top level /scans.json is ignored/causes error although recommended to be used in the next msg #742

Closed
yarikoptic opened this issue Mar 6, 2019 · 4 comments · Fixed by #1200
Labels

Comments

@yarikoptic
Copy link
Contributor

$ singularity exec -e -B $PWD ~yoh/bin/bids-validator.simg  bids-validator -c .bids-validator.cfg $PWD
1: [ERR] Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder. (code: 1 - NOT_INCLUDED)
                ./scans.json
                        Evidence: scans.json

1: [WARN] Tabular file contains custom columns not described in a data dictionary (code: 82 - CUSTOM_COLUMN_WITHOUT_DESCRIPTION)
   ./sub-sid000003/ses-XXX/sub-sid000003_ses-XXX_scans.tsv
         Evidence: Columns: operator, randstr not defined, please define in: /scans.json, /sub-sid000003/sub-sid000003_scans.json,/sub-sid000003/ses-XXX/sub-sid000003_ses-XXX_scans.json
...

copying scans.tsv under a corresponding subject's directory near the _scans.tsv resolves it for that subject.

@yarikoptic
Copy link
Contributor Author

could it be upgraded to "top one" priority (unless somehow it is a complicated fix)? ;-) I keep tripping on this one.

@sappelhoff
Copy link
Member

probably related to #1119

@sappelhoff sappelhoff added the bug label Feb 12, 2021
@sappelhoff
Copy link
Member

same as in #1119 (comment), this can probably be fixed by adding scans.json to this part of the code:

{
"root_top": {
"regexp": "^[\\/\\\\]?(@@@_root_files_@@@)$",
"tokens": {
"@@@_root_files_@@@": [
"README",
"CHANGES",
"LICENSE",
"dataset_description.json",
"genetic_info.json",
"participants.tsv",
"participants.json",
"phasediff.json",
"phase1.json",
"phase2.json",
"fieldmap.json"
]
}
},

@effigies
Copy link
Collaborator

Makes sense to me.

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

Successfully merging a pull request may close this issue.

4 participants