BIDS Validation
3 Errors InvalidError: 110 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./core.1473
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.
core.1473
/core.19030
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.
core.19030
/core.22312
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.
core.22312
/core.22568
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.
core.22568
/core.23291
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.
core.23291
/core.24381
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.
core.24381
/core.25190
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.
core.25190
/core.2770
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.
core.2770
/core.5085
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.
core.5085
/core.6196
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.
core.6196
Error: 22 files
This file is too small to contain the minimal NIfTI header./sub-01/ses-00/anat/sub-01_ses-00_acq-spc_T2w.nii.gz
This file is too small to contain the minimal NIfTI header.
/sub-01/ses-00/dwi/sub-01_ses-00_dwi.nii.gz
This file is too small to contain the minimal NIfTI header.
Error: 32 files
Empty files not allowed./sub-01/ses-00/anat/sub-01_ses-00_acq-spc_T2w.nii.gz
Empty files (/datalad/ds000244/sub-01/ses-00/anat/sub-01_ses-00_acq-spc_T2w.nii.gz) not allowed.
/sub-01/ses-00/dwi/sub-01_ses-00_dwi.nii.gz
Empty files (/datalad/ds000244/sub-01/ses-00/dwi/sub-01_ses-00_dwi.nii.gz) not allowed.
Warning: 13 files
A proper way of labeling missing values is "n/a"./sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFaces_dir-ap_events.tsv
Missing value at column # 4
row 34: 239.72 10.0 face_too-slow nan
/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFood_dir-pa_events.tsv
Missing value at column # 4
row 26: 193.647 10.0 food_too-slow nan
/sub-05/ses-15/func/sub-05_ses-15_task-PreferencePaintings_dir-ap_events.tsv
Missing value at column # 4
row 38: 234.434 10.0 painting_too-slow nan
Warning: 241 files
Task scans should have a corresponding events.tsv file. If this is a resting state scan you can ignore this warning or rename the task to include the word "rest"./sub-01/ses-14/func/sub-01_ses-14_task-RestingState_acq-ap_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_acq-ap_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-01/sub-01_task-RestingState_acq-ap_events.tsv, /sub-01/sub-01_task-RestingState_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/ses-14/sub-01_ses-14_task-RestingState_acq-ap_events.tsv, /sub-01/ses-14/sub-01_ses-14_task-RestingState_events.tsv, /sub-01/ses-14/sub-01_ses-14_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_task-RestingState_acq-ap_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_task-RestingState_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_events.tsv
/sub-01/ses-14/func/sub-01_ses-14_task-RestingState_acq-pa_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_acq-pa_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-01/sub-01_task-RestingState_acq-pa_events.tsv, /sub-01/sub-01_task-RestingState_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/ses-14/sub-01_ses-14_task-RestingState_acq-pa_events.tsv, /sub-01/ses-14/sub-01_ses-14_task-RestingState_events.tsv, /sub-01/ses-14/sub-01_ses-14_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_task-RestingState_acq-pa_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_task-RestingState_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_events.tsv
/sub-01/ses-14/func/sub-01_ses-14_task-RestingState_dir-ap_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_dir-ap_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-01/sub-01_task-RestingState_dir-ap_events.tsv, /sub-01/sub-01_task-RestingState_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/ses-14/sub-01_ses-14_task-RestingState_dir-ap_events.tsv, /sub-01/ses-14/sub-01_ses-14_task-RestingState_events.tsv, /sub-01/ses-14/sub-01_ses-14_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_task-RestingState_dir-ap_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_task-RestingState_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_events.tsv
/sub-01/ses-14/func/sub-01_ses-14_task-RestingState_dir-pa_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_dir-pa_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-01/sub-01_task-RestingState_dir-pa_events.tsv, /sub-01/sub-01_task-RestingState_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/ses-14/sub-01_ses-14_task-RestingState_dir-pa_events.tsv, /sub-01/ses-14/sub-01_ses-14_task-RestingState_events.tsv, /sub-01/ses-14/sub-01_ses-14_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_task-RestingState_dir-pa_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_task-RestingState_events.tsv, /sub-01/ses-14/func/sub-01_ses-14_events.tsv
/sub-01/ses-15/func/sub-01_ses-15_task-RestingState_acq-ap_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_acq-ap_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-01/sub-01_task-RestingState_acq-ap_events.tsv, /sub-01/sub-01_task-RestingState_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/ses-15/sub-01_ses-15_task-RestingState_acq-ap_events.tsv, /sub-01/ses-15/sub-01_ses-15_task-RestingState_events.tsv, /sub-01/ses-15/sub-01_ses-15_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_task-RestingState_acq-ap_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_task-RestingState_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_events.tsv
/sub-01/ses-15/func/sub-01_ses-15_task-RestingState_acq-pa_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_acq-pa_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-01/sub-01_task-RestingState_acq-pa_events.tsv, /sub-01/sub-01_task-RestingState_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/ses-15/sub-01_ses-15_task-RestingState_acq-pa_events.tsv, /sub-01/ses-15/sub-01_ses-15_task-RestingState_events.tsv, /sub-01/ses-15/sub-01_ses-15_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_task-RestingState_acq-pa_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_task-RestingState_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_events.tsv
/sub-01/ses-15/func/sub-01_ses-15_task-RestingState_dir-ap_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_dir-ap_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-01/sub-01_task-RestingState_dir-ap_events.tsv, /sub-01/sub-01_task-RestingState_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/ses-15/sub-01_ses-15_task-RestingState_dir-ap_events.tsv, /sub-01/ses-15/sub-01_ses-15_task-RestingState_events.tsv, /sub-01/ses-15/sub-01_ses-15_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_task-RestingState_dir-ap_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_task-RestingState_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_events.tsv
/sub-01/ses-15/func/sub-01_ses-15_task-RestingState_dir-pa_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_dir-pa_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-01/sub-01_task-RestingState_dir-pa_events.tsv, /sub-01/sub-01_task-RestingState_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/ses-15/sub-01_ses-15_task-RestingState_dir-pa_events.tsv, /sub-01/ses-15/sub-01_ses-15_task-RestingState_events.tsv, /sub-01/ses-15/sub-01_ses-15_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_task-RestingState_dir-pa_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_task-RestingState_events.tsv, /sub-01/ses-15/func/sub-01_ses-15_events.tsv
/sub-04/ses-11/func/sub-04_ses-11_task-RestingState_dir-ap_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_dir-ap_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-04/sub-04_task-RestingState_dir-ap_events.tsv, /sub-04/sub-04_task-RestingState_events.tsv, /sub-04/sub-04_events.tsv, /sub-04/ses-11/sub-04_ses-11_task-RestingState_dir-ap_events.tsv, /sub-04/ses-11/sub-04_ses-11_task-RestingState_events.tsv, /sub-04/ses-11/sub-04_ses-11_events.tsv, /sub-04/ses-11/func/sub-04_ses-11_task-RestingState_dir-ap_events.tsv, /sub-04/ses-11/func/sub-04_ses-11_task-RestingState_events.tsv, /sub-04/ses-11/func/sub-04_ses-11_events.tsv
/sub-04/ses-11/func/sub-04_ses-11_task-RestingState_dir-pa_bold.nii.gz
Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /task-RestingState_dir-pa_events.tsv, /task-RestingState_events.tsv, /events.tsv, /sub-04/sub-04_task-RestingState_dir-pa_events.tsv, /sub-04/sub-04_task-RestingState_events.tsv, /sub-04/sub-04_events.tsv, /sub-04/ses-11/sub-04_ses-11_task-RestingState_dir-pa_events.tsv, /sub-04/ses-11/sub-04_ses-11_task-RestingState_events.tsv, /sub-04/ses-11/sub-04_ses-11_events.tsv, /sub-04/ses-11/func/sub-04_ses-11_task-RestingState_dir-pa_events.tsv, /sub-04/ses-11/func/sub-04_ses-11_task-RestingState_events.tsv, /sub-04/ses-11/func/sub-04_ses-11_events.tsv
Warning: 34711 files
Not all subjects contain the same files. Each subject should contain the same number of files with the same naming unless some files are known to be missing./sub-01/ses-00/dwi/sub-01_ses-00_acq-sbref_dwi.bval
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-00_acq-sbref_dwi.bval
/sub-01/ses-00/dwi/sub-01_ses-00_acq-sbref_dwi.bvec
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-00_acq-sbref_dwi.bvec
/sub-01/ses-00/dwi/sub-01_ses-00_acq-sbref_dwi.nii.gz
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-00_acq-sbref_dwi.nii.gz
/sub-01/ses-03/func/sub-01_ses-03_task-ArchiEmotional_acq-ap_bold.nii.gz
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-03_task-ArchiEmotional_acq-ap_bold.nii.gz
/sub-01/ses-03/func/sub-01_ses-03_task-ArchiEmotional_acq-ap_events.tsv
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-03_task-ArchiEmotional_acq-ap_events.tsv
/sub-01/ses-03/func/sub-01_ses-03_task-ArchiEmotional_acq-pa_bold.nii.gz
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-03_task-ArchiEmotional_acq-pa_bold.nii.gz
/sub-01/ses-03/func/sub-01_ses-03_task-ArchiEmotional_acq-pa_events.tsv
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-03_task-ArchiEmotional_acq-pa_events.tsv
/sub-01/ses-03/func/sub-01_ses-03_task-ArchiEmotional_acq-pa_sbref.nii.gz
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-03_task-ArchiEmotional_acq-pa_sbref.nii.gz
/sub-01/ses-03/func/sub-01_ses-03_task-ArchiEmotional_dir-ap_bold.nii.gz
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-03_task-ArchiEmotional_dir-ap_bold.nii.gz
/sub-01/ses-03/func/sub-01_ses-03_task-ArchiEmotional_dir-ap_events.tsv
This file is missing for subject sub-01, but is present for at least one other subject.
Subject: sub-01; Missing file: sub-01_ses-03_task-ArchiEmotional_dir-ap_events.tsv
Warning: 4169 files
Not all subjects/sessions/runs have the same scanning parameters./sub-01/ses-00/anat/sub-01_ses-00_FLAIR.nii.gz
The most common set of dimensions is: 512,512,192 (voxels), This file has the dimensions: 512,512,160 (voxels).
/sub-01/ses-00/anat/sub-01_ses-00_T1w.nii.gz
The most common resolution is: 1.00mm x 1.00mm x 1.00mm, This file has the resolution: 1.00mm x 1.00mm x 1.10mm.
/sub-01/ses-24/func/sub-01_ses-24_task-Self_dir-ap_run-04_bold.nii.gz
The most common set of dimensions is: 128,128,93,359 (voxels), This file has the dimensions: 128,128,93,480 (voxels).
/sub-02/ses-00/anat/sub-02_ses-00_FLAIR.nii.gz
The most common set of dimensions is: 512,512,192 (voxels), This file has the dimensions: 512,512,160 (voxels). The most common resolution is: 0.45mm x 0.45mm x 0.81mm, This file has the resolution: 0.45mm x 0.45mm x 0.90mm.
/sub-02/ses-00/dwi/sub-02_ses-00_dwi.nii.gz
The most common set of dimensions is: 120,120,70,21 (voxels), This file has the dimensions: 96,96,64,22 (voxels). The most common resolution is: 2.00mm x 2.00mm x 2.00mm x 9.00s, This file has the resolution: 2.00mm x 2.00mm x 2.00mm x 4.10s.
/sub-02/ses-01/fmap/sub-02_ses-01_dir-0_epi.nii.gz
The most common set of dimensions is: 128,128,93 (voxels), This file has the dimensions: 128,128,84 (voxels).
/sub-02/ses-01/fmap/sub-02_ses-01_dir-1_epi.nii.gz
The most common set of dimensions is: 128,128,93 (voxels), This file has the dimensions: 128,128,84 (voxels).
/sub-02/ses-01/fmap/sub-02_ses-01_dir-ap_epi.nii.gz
The most common set of dimensions is: 128,128,93 (voxels), This file has the dimensions: 128,128,84 (voxels).
/sub-02/ses-01/fmap/sub-02_ses-01_dir-pa_epi.nii.gz
The most common set of dimensions is: 128,128,93 (voxels), This file has the dimensions: 128,128,84 (voxels).
/sub-02/ses-01/func/sub-02_ses-01_task-ArchiEmotional_acq-ap_bold.nii.gz
The most common set of dimensions is: 128,128,93,220 (voxels), This file has the dimensions: 128,128,84,220 (voxels).
Warning: 54 files
NIfTI file's header field for unit information for x, y, z, and t dimensions empty or too short/sub-01/ses-00/anat/sub-01_ses-00_FLAIR.nii.gz
NIfTI file's header field for unit information for x, y, z, and t dimensions empty or too short
/sub-01/ses-00/anat/sub-01_ses-00_acq-tse_T2w.nii.gz
NIfTI file's header field for unit information for x, y, z, and t dimensions empty or too short
/sub-08/ses-00/anat/sub-08_ses-00_FLAIR.nii.gz
NIfTI file's header field for unit information for x, y, z, and t dimensions empty or too short
/sub-08/ses-00/anat/sub-08_ses-00_acq-spc_T2w.nii.gz
NIfTI file's header field for unit information for x, y, z, and t dimensions empty or too short
Warning: 665 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: handedness score not defined, please define in: /participants.json
/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFaces_dir-ap_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferenceFaces_dir-ap_events.json, /task-PreferenceFaces_events.json,/events.json,/sub-01/sub-01_task-PreferenceFaces_dir-ap_events.json,/sub-01/sub-01_task-PreferenceFaces_events.json,/sub-01/sub-01_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceFaces_dir-ap_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceFaces_events.json,/sub-01/ses-19/sub-01_ses-19_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFaces_dir-ap_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFaces_events.json,/sub-01/ses-19/func/sub-01_ses-19_events.json
/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFaces_dir-pa_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferenceFaces_dir-pa_events.json, /task-PreferenceFaces_events.json,/events.json,/sub-01/sub-01_task-PreferenceFaces_dir-pa_events.json,/sub-01/sub-01_task-PreferenceFaces_events.json,/sub-01/sub-01_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceFaces_dir-pa_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceFaces_events.json,/sub-01/ses-19/sub-01_ses-19_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFaces_dir-pa_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFaces_events.json,/sub-01/ses-19/func/sub-01_ses-19_events.json
/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFood_dir-ap_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferenceFood_dir-ap_events.json, /task-PreferenceFood_events.json,/events.json,/sub-01/sub-01_task-PreferenceFood_dir-ap_events.json,/sub-01/sub-01_task-PreferenceFood_events.json,/sub-01/sub-01_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceFood_dir-ap_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceFood_events.json,/sub-01/ses-19/sub-01_ses-19_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFood_dir-ap_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFood_events.json,/sub-01/ses-19/func/sub-01_ses-19_events.json
/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFood_dir-pa_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferenceFood_dir-pa_events.json, /task-PreferenceFood_events.json,/events.json,/sub-01/sub-01_task-PreferenceFood_dir-pa_events.json,/sub-01/sub-01_task-PreferenceFood_events.json,/sub-01/sub-01_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceFood_dir-pa_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceFood_events.json,/sub-01/ses-19/sub-01_ses-19_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFood_dir-pa_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceFood_events.json,/sub-01/ses-19/func/sub-01_ses-19_events.json
/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceHouses_dir-ap_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferenceHouses_dir-ap_events.json, /task-PreferenceHouses_events.json,/events.json,/sub-01/sub-01_task-PreferenceHouses_dir-ap_events.json,/sub-01/sub-01_task-PreferenceHouses_events.json,/sub-01/sub-01_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceHouses_dir-ap_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceHouses_events.json,/sub-01/ses-19/sub-01_ses-19_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceHouses_dir-ap_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceHouses_events.json,/sub-01/ses-19/func/sub-01_ses-19_events.json
/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceHouses_dir-pa_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferenceHouses_dir-pa_events.json, /task-PreferenceHouses_events.json,/events.json,/sub-01/sub-01_task-PreferenceHouses_dir-pa_events.json,/sub-01/sub-01_task-PreferenceHouses_events.json,/sub-01/sub-01_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceHouses_dir-pa_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferenceHouses_events.json,/sub-01/ses-19/sub-01_ses-19_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceHouses_dir-pa_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferenceHouses_events.json,/sub-01/ses-19/func/sub-01_ses-19_events.json
/sub-01/ses-19/func/sub-01_ses-19_task-PreferencePaintings_dir-ap_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferencePaintings_dir-ap_events.json, /task-PreferencePaintings_events.json,/events.json,/sub-01/sub-01_task-PreferencePaintings_dir-ap_events.json,/sub-01/sub-01_task-PreferencePaintings_events.json,/sub-01/sub-01_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferencePaintings_dir-ap_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferencePaintings_events.json,/sub-01/ses-19/sub-01_ses-19_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferencePaintings_dir-ap_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferencePaintings_events.json,/sub-01/ses-19/func/sub-01_ses-19_events.json
/sub-01/ses-19/func/sub-01_ses-19_task-PreferencePaintings_dir-pa_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferencePaintings_dir-pa_events.json, /task-PreferencePaintings_events.json,/events.json,/sub-01/sub-01_task-PreferencePaintings_dir-pa_events.json,/sub-01/sub-01_task-PreferencePaintings_events.json,/sub-01/sub-01_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferencePaintings_dir-pa_events.json,/sub-01/ses-19/sub-01_ses-19_task-PreferencePaintings_events.json,/sub-01/ses-19/sub-01_ses-19_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferencePaintings_dir-pa_events.json,/sub-01/ses-19/func/sub-01_ses-19_task-PreferencePaintings_events.json,/sub-01/ses-19/func/sub-01_ses-19_events.json
/sub-04/ses-15/func/sub-04_ses-15_task-PreferenceFaces_dir-ap_events.tsv
Tabular file contains custom columns not described in a data dictionary
Columns: score not defined, please define in: /task-PreferenceFaces_dir-ap_events.json, /task-PreferenceFaces_events.json,/events.json,/sub-04/sub-04_task-PreferenceFaces_dir-ap_events.json,/sub-04/sub-04_task-PreferenceFaces_events.json,/sub-04/sub-04_events.json,/sub-04/ses-15/sub-04_ses-15_task-PreferenceFaces_dir-ap_events.json,/sub-04/ses-15/sub-04_ses-15_task-PreferenceFaces_events.json,/sub-04/ses-15/sub-04_ses-15_events.json,/sub-04/ses-15/func/sub-04_ses-15_task-PreferenceFaces_dir-ap_events.json,/sub-04/ses-15/func/sub-04_ses-15_task-PreferenceFaces_events.json,/sub-04/ses-15/func/sub-04_ses-15_events.json
Warning: 710 files
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long./sub-02/ses-04/func/sub-02_ses-04_task-HcpLanguage_dir-pa_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-05/ses-01/func/sub-05_ses-01_task-HcpLanguage_dir-pa_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-05/ses-03/func/sub-05_ses-03_task-RSVPLanguage00_acq-pa_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-05/ses-03/func/sub-05_ses-03_task-RSVPLanguage_dir-pa_run-00_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-07/ses-00/func/sub-07_ses-00_task-ArchiSpatial_acq-ap_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-07/ses-00/func/sub-07_ses-00_task-ArchiSpatial_dir-ap_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-08/ses-02/func/sub-08_ses-02_task-HcpLanguage_dir-pa_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-11/ses-11/func/sub-11_ses-11_task-MTTWE_dir-ap_run-03_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-12/ses-01/func/sub-12_ses-01_task-HcpLanguage_dir-pa_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
/sub-13/ses-01/func/sub-13_ses-01_task-HcpLanguage_dir-pa_events.tsv
The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.
Warning: 81 file
The onset of the last event is less than half the total duration of the corresponding scan. This design is suspiciously short./sub-08/ses-11/func/sub-08_ses-11_task-MTTWE_dir-ap_run-03_events.tsv
The onset of the last event is less than half the total duration of the corresponding scan. This design is suspiciously short.
Warning: 984 files
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume./sub-01/ses-00/func/sub-01_ses-00_task-ArchiSocial_acq-ap_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiSocial_acq-pa_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiSocial_dir-ap_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiSocial_dir-pa_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiSpatial_acq-ap_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiSpatial_acq-pa_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiSpatial_dir-ap_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiSpatial_dir-pa_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiStandard_acq-ap_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
/sub-01/ses-00/func/sub-01_ses-00_task-ArchiStandard_acq-pa_bold.nii.gz
The number of elements in the SliceTiming array should match the 'k' dimension of the corresponding NIfTI volume.
SliceTiming array is of length 93 and the value of the 'k' dimension is 84 for the corresponding nifti header.
Warning: 10161 files
Not all subjects contain the same sessions./sub-01/ses-01
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-01
/sub-01/ses-02
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-02
/sub-01/ses-06
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-06
/sub-01/ses-11
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-11
/sub-01/ses-12
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-12
/sub-01/ses-13
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-13
/sub-01/ses-16
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-16
/sub-01/ses-17
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-17
/sub-01/ses-18
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-18
/sub-01/ses-21
A session is missing from one subject that is present in at least one other subject
Subject: sub-01; Missing session: ses-21
Comments