File Path: 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. Type: Error File: sub-B1001_ses-01_FLAIR.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.json Reason: 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. Evidence: sub-B1001_ses-01_FLAIR.json Type: Error File: sub-B1001_ses-01_FLAIR.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_FLAIR.nii.gz Type: Error File: sub-B1001_ses-01_T1w.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T1w.json Reason: 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. Evidence: sub-B1001_ses-01_T1w.json Type: Error File: sub-B1001_ses-01_T1w.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T1w.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_T1w.nii.gz Type: Error File: sub-B1001_ses-01_T2w.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T2w.json Reason: 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. Evidence: sub-B1001_ses-01_T2w.json Type: Error File: sub-B1001_ses-01_T2w.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T2w.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_T2w.nii.gz Type: Error File: sub-B1001_ses-01_dwi.bval Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bval Reason: 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. Evidence: sub-B1001_ses-01_dwi.bval Type: Error File: sub-B1001_ses-01_dwi.bvec Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bvec Reason: 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. Evidence: sub-B1001_ses-01_dwi.bvec Type: Error File: sub-B1001_ses-01_dwi.json Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.json Reason: 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. Evidence: sub-B1001_ses-01_dwi.json Type: Error File: sub-B1001_ses-01_dwi.nii.gz Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_dwi.nii.gz Type: Error File: sub-B1001_ses-01_task-CRT_run-01_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.json Reason: 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. Evidence: sub-B1001_ses-01_task-CRT_run-01_bold.json Type: Error File: sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz Type: Error File: sub-B1001_ses-01_task-CRT_run-02_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.json Reason: 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. Evidence: sub-B1001_ses-01_task-CRT_run-02_bold.json Type: Error File: sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz Type: Error File: sub-B1001_ses-01_task-CRT_run-03_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.json Reason: 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. Evidence: sub-B1001_ses-01_task-CRT_run-03_bold.json Type: Error File: sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz Type: Error File: sub-B1001_ses-01_task-rest_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.json Reason: 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. Evidence: sub-B1001_ses-01_task-rest_bold.json Type: Error File: sub-B1001_ses-01_task-rest_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_task-rest_bold.nii.gz Type: Error File: sub-B1001_ses-01_pcasl.json Location: bids_project/B1001/ses-01/perf/sub-B1001_ses-01_pcasl.json Reason: 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. Evidence: sub-B1001_ses-01_pcasl.json Type: Error File: sub-B1001_ses-01_pcasl.nii.gz Location: bids_project/B1001/ses-01/perf/sub-B1001_ses-01_pcasl.nii.gz Reason: 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. Evidence: sub-B1001_ses-01_pcasl.nii.gz ====================================================== File Path: There are no subject folders (labeled "sub-*") in the root of this dataset. Type: Error ====================================================== File Path: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Type: Error File: sub-B1001_ses-01_FLAIR.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_FLAIR.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.nii.gz is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_T1w.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T1w.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_T1w.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_T1w.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T1w.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_T1w.nii.gz is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_T2w.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T2w.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_T2w.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_T2w.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T2w.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_T2w.nii.gz is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_dwi.bval Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bval Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bval is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_dwi.bvec Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bvec Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bvec is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_dwi.json Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/dwi/sub-B1001_ses-01_dwi.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_dwi.nii.gz Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/dwi/sub-B1001_ses-01_dwi.nii.gz is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-01_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-02_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-03_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_task-rest_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_task-rest_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.nii.gz is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_pcasl.json Location: bids_project/B1001/ses-01/perf/sub-B1001_ses-01_pcasl.json Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/perf/sub-B1001_ses-01_pcasl.json is saved in incorrect subject directory as per sub-id in filename. Type: Error File: sub-B1001_ses-01_pcasl.nii.gz Location: bids_project/B1001/ses-01/perf/sub-B1001_ses-01_pcasl.nii.gz Reason: Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory. Evidence: File: /B1001/ses-01/perf/sub-B1001_ses-01_pcasl.nii.gz is saved in incorrect subject directory as per sub-id in filename. ====================================================== File Path: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Type: Error File: sub-B1001_ses-01_FLAIR.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_FLAIR.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_FLAIR.nii.gz is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_T1w.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T1w.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_T1w.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_T1w.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T1w.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_T1w.nii.gz is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_T2w.json Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T2w.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_T2w.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_T2w.nii.gz Location: bids_project/B1001/ses-01/anat/sub-B1001_ses-01_T2w.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/anat/sub-B1001_ses-01_T2w.nii.gz is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_dwi.bval Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bval Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bval is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_dwi.bvec Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bvec Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/dwi/sub-B1001_ses-01_dwi.bvec is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_dwi.json Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/dwi/sub-B1001_ses-01_dwi.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_dwi.nii.gz Location: bids_project/B1001/ses-01/dwi/sub-B1001_ses-01_dwi.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/dwi/sub-B1001_ses-01_dwi.nii.gz is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-01_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-01_bold.nii.gz is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-02_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-02_bold.nii.gz is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-03_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-CRT_run-03_bold.nii.gz is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_task-rest_bold.json Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_task-rest_bold.nii.gz Location: bids_project/B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/func/sub-B1001_ses-01_task-rest_bold.nii.gz is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_pcasl.json Location: bids_project/B1001/ses-01/perf/sub-B1001_ses-01_pcasl.json Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/perf/sub-B1001_ses-01_pcasl.json is saved in incorrect session directory as per ses-id in filename. Type: Error File: sub-B1001_ses-01_pcasl.nii.gz Location: bids_project/B1001/ses-01/perf/sub-B1001_ses-01_pcasl.nii.gz Reason: Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory. Evidence: File: /B1001/ses-01/perf/sub-B1001_ses-01_pcasl.nii.gz is saved in incorrect session directory as per ses-id in filename. ====================================================== File Path: Tabular file contains custom columns not described in a data dictionary Type: Warning File: participants.tsv Location: bids_project/participants.tsv Reason: Tabular file contains custom columns not described in a data dictionary Evidence: Columns: age, sex, group not defined, please define in: /participants.json ====================================================== File Path: The Authors field of dataset_description.json should contain an array of fields - with one author per field. This was triggered based on the presence of only one author field. Please ignore if all contributors are already properly listed. Type: Warning ====================================================== File Path: The Name field of dataset_description.json is present but empty of visible characters. Type: Warning ======================================================