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-1600001_ses-01_acq-98_dir-AP_dwi.bval Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-AP_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-1600001_ses-01_acq-98_dir-AP_dwi.bval Type: Error File: sub-1600001_ses-01_acq-98_dir-AP_dwi.bvec Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-AP_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-1600001_ses-01_acq-98_dir-AP_dwi.bvec Type: Error File: sub-1600001_ses-01_acq-98_dir-AP_dwi.json Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-AP_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-1600001_ses-01_acq-98_dir-AP_dwi.json Type: Error File: sub-1600001_ses-01_acq-98_dir-AP_dwi.nii.gz Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-AP_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-1600001_ses-01_acq-98_dir-AP_dwi.nii.gz Type: Error File: sub-1600001_ses-01_acq-98_dir-AP_sbref.json Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-AP_sbref.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-1600001_ses-01_acq-98_dir-AP_sbref.json Type: Error File: sub-1600001_ses-01_acq-98_dir-AP_sbref.nii.gz Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-AP_sbref.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-1600001_ses-01_acq-98_dir-AP_sbref.nii.gz Type: Error File: sub-1600001_ses-01_acq-98_dir-PA_dwi.json Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-PA_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-1600001_ses-01_acq-98_dir-PA_dwi.json Type: Error File: sub-1600001_ses-01_acq-98_dir-PA_dwi.nii.gz Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-PA_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-1600001_ses-01_acq-98_dir-PA_dwi.nii.gz Type: Error File: sub-1600001_ses-01_acq-98_dir-PA_sbref.json Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-PA_sbref.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-1600001_ses-01_acq-98_dir-PA_sbref.json Type: Error File: sub-1600001_ses-01_acq-98_dir-PA_sbref.nii.gz Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-98_dir-PA_sbref.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-1600001_ses-01_acq-98_dir-PA_sbref.nii.gz Type: Error File: sub-1600001_ses-01_acq-99_dir-AP_dwi.bval Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-AP_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-1600001_ses-01_acq-99_dir-AP_dwi.bval Type: Error File: sub-1600001_ses-01_acq-99_dir-AP_dwi.bvec Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-AP_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-1600001_ses-01_acq-99_dir-AP_dwi.bvec Type: Error File: sub-1600001_ses-01_acq-99_dir-AP_dwi.json Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-AP_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-1600001_ses-01_acq-99_dir-AP_dwi.json Type: Error File: sub-1600001_ses-01_acq-99_dir-AP_dwi.nii.gz Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-AP_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-1600001_ses-01_acq-99_dir-AP_dwi.nii.gz Type: Error File: sub-1600001_ses-01_acq-99_dir-AP_sbref.json Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-AP_sbref.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-1600001_ses-01_acq-99_dir-AP_sbref.json Type: Error File: sub-1600001_ses-01_acq-99_dir-AP_sbref.nii.gz Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-AP_sbref.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-1600001_ses-01_acq-99_dir-AP_sbref.nii.gz Type: Error File: sub-1600001_ses-01_acq-99_dir-PA_dwi.json Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-PA_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-1600001_ses-01_acq-99_dir-PA_dwi.json Type: Error File: sub-1600001_ses-01_acq-99_dir-PA_dwi.nii.gz Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-PA_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-1600001_ses-01_acq-99_dir-PA_dwi.nii.gz Type: Error File: sub-1600001_ses-01_acq-99_dir-PA_sbref.json Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-PA_sbref.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-1600001_ses-01_acq-99_dir-PA_sbref.json Type: Error File: sub-1600001_ses-01_acq-99_dir-PA_sbref.nii.gz Location: ACon1/sub-1600001/ses-01/dwi/sub-1600001_ses-01_acq-99_dir-PA_sbref.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-1600001_ses-01_acq-99_dir-PA_sbref.nii.gz ====================================================== File Path: Tabular file contains custom columns not described in a data dictionary Type: Warning File: participants.tsv Location: ACon1/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 Type: Warning File: sub-1600001_ses-01_task-encoding_run-01_events.tsv Location: ACon1/sub-1600001/ses-01/func/sub-1600001_ses-01_task-encoding_run-01_events.tsv Reason: Tabular file contains custom columns not described in a data dictionary Evidence: Columns: TODO -- fill in rows and add more tab-separated columns if desired not defined, please define in: /sub-1600001/ses-01/func/sub-1600001_ses-01_events.json, /sub-1600001/ses-01/func/sub-1600001_ses-01_task-encoding_events.json,/sub-1600001/ses-01/sub-1600001_ses-01_events.json,/sub-1600001/ses-01/sub-1600001_ses-01_task-encoding_events.json,/sub-1600001/sub-1600001_events.json,/sub-1600001/sub-1600001_task-encoding_events.json,/events.json,/task-encoding_events.json,/sub-1600001/ses-01/func/sub-1600001_ses-01_task-encoding_run-01_events.json Type: Warning File: sub-1600001_ses-01_task-encoding_run-02_events.tsv Location: ACon1/sub-1600001/ses-01/func/sub-1600001_ses-01_task-encoding_run-02_events.tsv Reason: Tabular file contains custom columns not described in a data dictionary Evidence: Columns: TODO -- fill in rows and add more tab-separated columns if desired not defined, please define in: /sub-1600001/ses-01/func/sub-1600001_ses-01_events.json, /sub-1600001/ses-01/func/sub-1600001_ses-01_task-encoding_events.json,/sub-1600001/ses-01/sub-1600001_ses-01_events.json,/sub-1600001/ses-01/sub-1600001_ses-01_task-encoding_events.json,/sub-1600001/sub-1600001_events.json,/sub-1600001/sub-1600001_task-encoding_events.json,/events.json,/task-encoding_events.json,/sub-1600001/ses-01/func/sub-1600001_ses-01_task-encoding_run-02_events.json Type: Warning File: sub-1600001_ses-01_task-rest_run-01_events.tsv Location: ACon1/sub-1600001/ses-01/func/sub-1600001_ses-01_task-rest_run-01_events.tsv Reason: Tabular file contains custom columns not described in a data dictionary Evidence: Columns: TODO -- fill in rows and add more tab-separated columns if desired not defined, please define in: /sub-1600001/ses-01/func/sub-1600001_ses-01_events.json, /sub-1600001/ses-01/func/sub-1600001_ses-01_task-rest_events.json,/sub-1600001/ses-01/sub-1600001_ses-01_events.json,/sub-1600001/ses-01/sub-1600001_ses-01_task-rest_events.json,/sub-1600001/sub-1600001_events.json,/sub-1600001/sub-1600001_task-rest_events.json,/events.json,/task-rest_events.json,/sub-1600001/ses-01/func/sub-1600001_ses-01_task-rest_run-01_events.json Type: Warning File: sub-1600001_ses-01_task-rest_run-02_events.tsv Location: ACon1/sub-1600001/ses-01/func/sub-1600001_ses-01_task-rest_run-02_events.tsv Reason: Tabular file contains custom columns not described in a data dictionary Evidence: Columns: TODO -- fill in rows and add more tab-separated columns if desired not defined, please define in: /sub-1600001/ses-01/func/sub-1600001_ses-01_events.json, /sub-1600001/ses-01/func/sub-1600001_ses-01_task-rest_events.json,/sub-1600001/ses-01/sub-1600001_ses-01_events.json,/sub-1600001/ses-01/sub-1600001_ses-01_task-rest_events.json,/sub-1600001/sub-1600001_events.json,/sub-1600001/sub-1600001_task-rest_events.json,/events.json,/task-rest_events.json,/sub-1600001/ses-01/func/sub-1600001_ses-01_task-rest_run-02_events.json Type: Warning File: sub-1600001_ses-01_scans.tsv Location: ACon1/sub-1600001/ses-01/sub-1600001_ses-01_scans.tsv Reason: Tabular file contains custom columns not described in a data dictionary Evidence: Columns: operator, randstr not defined, please define in: /scans.json, /sub-1600001/sub-1600001_scans.json,/sub-1600001/ses-01/sub-1600001_ses-01_scans.json ======================================================