Invalid JSON file. The file is not formatted according the schema.

.MEGCoordinateSystem should be equal to one of the allowed values

Invalid JSON file. The file is not formatted according the schema.

.MEGCoordinateSystem should be equal to one of the allowed values

Invalid JSON file. The file is not formatted according the schema.

.MEGCoordinateSystem should be equal to one of the allowed values

Invalid JSON file. The file is not formatted according the schema.

.MEGCoordinateSystem should be equal to one of the allowed values

Invalid JSON file. The file is not formatted according the schema.

.MEGCoordinateSystem should match some schema in anyOf

Invalid JSON file. The file is not formatted according the schema.

.HeadCoilCoordinateSystem should be equal to one of the allowed values

Invalid JSON file. The file is not formatted according the schema.

.HeadCoilCoordinateSystem should be equal to one of the allowed values

Invalid JSON file. The file is not formatted according the schema.

.HeadCoilCoordinateSystem should be equal to one of the allowed values

Invalid JSON file. The file is not formatted according the schema.

.HeadCoilCoordinateSystem should be equal to one of the allowed values

Invalid JSON file. The file is not formatted according the schema.

.HeadCoilCoordinateSystem should match some schema in anyOf

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-01_ses-day1_task-AVLearn_run-01_part-01_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-01_ses-day1_task-AVLearn_run-01_part-02_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-03_ses-day1_task-AVLearn_run-01_part-01_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-03_ses-day1_task-AVLearn_run-01_part-02_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-04_ses-day1_task-AVLearn_run-01_part-01_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-04_ses-day1_task-AVLearn_run-01_part-02_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-05_ses-day1_task-AVLearn_run-01_part-01_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-05_ses-day1_task-AVLearn_run-01_part-02_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-06_ses-day1_task-AVLearn_run-01_part-01_meg.fif

Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

sub-06_ses-day1_task-AVLearn_run-01_part-02_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-01/ses-day1/meg/sub-01_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-03/ses-day1/meg/sub-03_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-04/ses-day1/meg/sub-04_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-05/ses-day1/meg/sub-05_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-06/ses-day1/meg/sub-06_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-07/ses-day1/meg/sub-07_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-08/ses-day1/meg/sub-08_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-11/ses-day1/meg/sub-11_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-12/ses-day1/meg/sub-12_ses-day1_task-AVLearn_run-01_meg.fif

The filename in scans.tsv file does not match what is present in the BIDS dataset.

Filename: /sub-13/ses-day1/meg/sub-13_ses-day1_task-AVLearn_run-01_meg.fif