BIDS Validation
3 Errors InvalidError: 16391 files
Invalid JSON file. The file is not formatted according the schema./dataset_description.json
Invalid JSON file. The file is not formatted according the schema.
.Funding should be array
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.json
Invalid JSON file. The file is not formatted according the schema.
['MatlabVersion'] should be object
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.json
Invalid JSON file. The file is not formatted according the schema.
['Begin'] should be object
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.json
Invalid JSON file. The file is not formatted according the schema.
['SubjID'] should be object
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.json
Invalid JSON file. The file is not formatted according the schema.
['RunNumber'] should be object
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.json
Invalid JSON file. The file is not formatted according the schema.
['AllTrials'] should be object
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.json
Invalid JSON file. The file is not formatted according the schema.
['ScreenResolution'] should be object
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_recording-cardiac_physio.json
Invalid JSON file. The file is not formatted according the schema.
.SamplingFrequency should be number
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_recording-cardiac_physio.json
Invalid JSON file. The file is not formatted according the schema.
.Columns should be array
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_recording-respiratory_physio.json
Invalid JSON file. The file is not formatted according the schema.
.SamplingFrequency should be number
Error: 2108 files
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./sub-CSI1/ses-01/fmap/sub-CSI1_ses-01_acq-PA_epi.json
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.
sub-CSI1_ses-01_acq-PA_epi.json
/sub-CSI1/ses-01/fmap/sub-CSI1_ses-01_acq-PA_epi.nii.gz
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.
sub-CSI1_ses-01_acq-PA_epi.nii.gz
/sub-CSI1/ses-02/fmap/sub-CSI1_ses-02_acq-PA_epi.json
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.
sub-CSI1_ses-02_acq-PA_epi.json
/sub-CSI1/ses-02/fmap/sub-CSI1_ses-02_acq-PA_epi.nii.gz
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.
sub-CSI1_ses-02_acq-PA_epi.nii.gz
/sub-CSI1/ses-03/fmap/sub-CSI1_ses-03_acq-PA_epi.json
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.
sub-CSI1_ses-03_acq-PA_epi.json
/sub-CSI1/ses-03/fmap/sub-CSI1_ses-03_acq-PA_epi.nii.gz
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.
sub-CSI1_ses-03_acq-PA_epi.nii.gz
/sub-CSI1/ses-04/fmap/sub-CSI1_ses-04_acq-PA_epi.json
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.
sub-CSI1_ses-04_acq-PA_epi.json
/sub-CSI1/ses-04/fmap/sub-CSI1_ses-04_acq-PA_epi.nii.gz
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.
sub-CSI1_ses-04_acq-PA_epi.nii.gz
/sub-CSI1/ses-05/fmap/sub-CSI1_ses-05_acq-PA_epi.json
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.
sub-CSI1_ses-05_acq-PA_epi.json
/sub-CSI1/ses-05/fmap/sub-CSI1_ses-05_acq-PA_epi.nii.gz
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.
sub-CSI1_ses-05_acq-PA_epi.nii.gz
Error: 318857 files
A stimulus file was declared but not found in the dataset./sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (n01930112_19568.JPEG) was declared but not found in /stimuli.
n01930112_19568.JPEG
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (n03733281_29214.JPEG) was declared but not found in /stimuli.
n03733281_29214.JPEG
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (n07695742_5848.JPEG) was declared but not found in /stimuli.
n07695742_5848.JPEG
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (COCO_train2014_000000420713.jpg) was declared but not found in /stimuli.
COCO_train2014_000000420713.jpg
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (COCO_train2014_000000488558.jpg) was declared but not found in /stimuli.
COCO_train2014_000000488558.jpg
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (n01917289_1429.JPEG) was declared but not found in /stimuli.
n01917289_1429.JPEG
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (n02108551_26574.JPEG) was declared but not found in /stimuli.
n02108551_26574.JPEG
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (COCO_train2014_000000029114.jpg) was declared but not found in /stimuli.
COCO_train2014_000000029114.jpg
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (n02111277_28582.JPEG) was declared but not found in /stimuli.
n02111277_28582.JPEG
/sub-CSI1/ses-01/func/sub-CSI1_ses-01_task-5000scenes_run-01_events.tsv
A stimulus file (concert5.jpg) was declared but not found in /stimuli.
concert5.jpg
Warning: 11 file
A proper way of labeling missing values is "n/a"./sub-CSI1/sub-CSI1_sessions.tsv
Missing value at column # 33
row 6: ses-06 2017-11-14 12:36:01 2017-11-14 12:43:38 100 456 2017-11-14 12:43:38 R_1gtguYU0hZNZcT5 1 11/14/17 2:41pm 6 Yes 2 hours ago Usual No n/a n/a 2 hours As much as usual No n/a n/a 7 As much as usual Yes 3 days ago As much as usual No n/a As much as usual 4 4 NA NA
Warning: 22 files
Not all subjects/sessions/runs have the same scanning parameters./sub-CSI2/ses-16/dwi/sub-CSI2_ses-16_acq-AP_dwi.nii.gz
The most common set of dimensions is: 106,106,72,253 (voxels), This file has the dimensions: 106,106,69,253 (voxels). The most common resolution is: 2.00mm x 2.00mm x 2.00mm x 4.15s, This file has the resolution: 2.00mm x 2.00mm x 2.00mm x 3.98s.
/sub-CSI2/ses-16/dwi/sub-CSI2_ses-16_acq-PA_dwi.nii.gz
The most common set of dimensions is: 106,106,72,253 (voxels), This file has the dimensions: 106,106,69,253 (voxels). The most common resolution is: 2.00mm x 2.00mm x 2.00mm x 4.15s, This file has the resolution: 2.00mm x 2.00mm x 2.00mm x 3.98s.
Warning: 35 files
Tabular file contains custom columns not described in a data dictionary/participants.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: age, sex, handedness not defined, please define in: /participants.json
/sub-CSI1/sub-CSI1_sessions.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: Start Date, End Date, Progress, Duration (in seconds), Recorded Date, Response ID, Subject ID, Date, Time, Session, Do you drink caffeinated beverages (i.e. coffee, tea, coke, etc.)?, If so, when was the last time you had a caffeinated beverage?, Is this..., Do you smoke?, If so, when was the last time you smoked?, Is this..., How long ago was your last meal?, At this point in the day, you have eaten..., Did you work out today?, If so, what was the activity, and how long ago?, Is this..., How many hours of sleep did you get last night?, Is this..., Do you drink alcoholic beverages?, If so, when was the last time you had an alcoholic beverage?, Is this..., Have you taken ibuprofen today (e.g. Advil, Motrin)?, If so, when was the last time you took it?, Is this..., In the scanner today I was physically: - Click to write Choice 1, In the scanner today I was mentally: - Click to write Choice 1, Please comment on which of these things, if any, are particularly different today and/or if you think they have affected your performance (for better or for worse):, Is there anything you think we should know about your experience in the MRI (e.g. were you tired, confused about task instructions, etc)? not defined, please define in: /sessions.json, /sub-CSI1/sub-CSI1_sessions.json
/sub-CSI2/sub-CSI2_sessions.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: Start Date, End Date, Duration (in seconds), Finished, Recorded Date, Response ID, Subject ID, Date, Time, Session, Do you drink caffeinated beverages (i.e. coffee, tea, coke, etc.)?, If so, when was the last time you had a caffeinated beverage?, Is this..., Do you smoke?, If so, when was the last time you smoked?, Is this..., How long ago was your last meal?, At this point in the day, you have eaten..., Did you work out today?, If so, what was the activity, and how long ago?, Is this..., How many hours of sleep did you get last night?, Is this..., Do you drink alcoholic beverages?, If so, when was the last time you had an alcoholic beverage?, Is this..., Have you taken ibuprofen today (e.g. Advil, Motrin)?, If so, when was the last time you took it?, Is this..., In the scanner today I was physically: - Click to write Choice 1, In the scanner today I was mentally: - Click to write Choice 1, Please comment on which of these things, if any, are particularly different today and/or if you think they have affected your performance (for better or for worse):, Is there anything you think we should know about your experience in the MRI (e.g. were you tired, confused about task instructions, etc)? not defined, please define in: /sessions.json, /sub-CSI2/sub-CSI2_sessions.json
/sub-CSI3/sub-CSI3_sessions.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: Start Date, End Date, Progress, Duration (in seconds), Recorded Date, Response ID, Subject ID, Date, Time, Session, Do you drink caffeinated beverages (i.e. coffee, tea, coke, etc.)?, If so, when was the last time you had a caffeinated beverage?, Is this..., Do you smoke?, If so, when was the last time you smoked?, Is this..., How long ago was your last meal?, At this point in the day, you have eaten..., Did you work out today?, If so, what was the activity, and how long ago?, Is this..., How many hours of sleep did you get last night?, Is this..., Do you drink alcoholic beverages?, If so, when was the last time you had an alcoholic beverage?, Is this..., Have you taken ibuprofen today (e.g. Advil, Motrin)?, If so, when was the last time you took it?, Is this..., In the scanner today I was physically: - Click to write Choice 1, In the scanner today I was mentally: - Click to write Choice 1, Please comment on which of these things, if any, are particularly different today and/or if you think they have affected your performance (for better or for worse):, Is there anything you think we should know about your experience in the MRI (e.g. were you tired, confused about task instructions, etc)? not defined, please define in: /sessions.json, /sub-CSI3/sub-CSI3_sessions.json
/sub-CSI4/sub-CSI4_sessions.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: Start Date, End Date, Duration (in seconds), Recorded Date, Response ID, Subject ID, Date, Time, Session, Do you drink caffeinated beverages (i.e. coffee, tea, coke, etc.)?, If so, when was the last time you had a caffeinated beverage?, Is this..., Do you smoke?, If so, when was the last time you smoked?, Is this..., How long ago was your last meal?, At this point in the day, you have eaten..., Did you work out today?, If so, what was the activity, and how long ago?, Is this..., How many hours of sleep did you get last night?, Is this..., Do you drink alcoholic beverages?, If so, when was the last time you had an alcoholic beverage?, Is this..., Have you taken ibuprofen today (e.g. Advil, Motrin)?, If so, when was the last time you took it?, Is this..., In the scanner today I was physically: - Click to write Choice 1, In the scanner today I was mentally: - Click to write Choice 1, Please comment on which of these things, if any, are particularly different today and/or if you think they have affected your performance (for better or for worse):, Is there anything you think we should know about your experience in the MRI (e.g. were you tired, confused about task instructions, etc)? not defined, please define in: /sessions.json, /sub-CSI4/sub-CSI4_sessions.json
Comments