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.

CHANGES

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.

README

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.

dataset_description.json

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

participants.tsv

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.

recording-cardresp_physio.json

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

recording-eyegaze_physio.json

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

LICENSE

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.

Makefile

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.

eyegaze_utils.py

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.

overlay_gaze_on_video

There are no subject folders (labeled "sub-*") in the root of this dataset.

The compulsory file /dataset_description.json is missing. See Section 03 (Modality agnostic files) of the BIDS specification.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-movielocalizer_run-1_bold.json is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-movielocalizer_run-1_bold.nii.gz is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-movielocalizer_run-1_defacemask.nii.gz is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-movielocalizer_run-1_recording-cardresp_physio.tsv.gz is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_bold.json is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_bold.nii.gz is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_defacemask.nii.gz is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_events.tsv is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_recording-cardresp_physio.tsv.gz is saved in incorrect subject directory as per sub-id in filename.

Subject label in the filename doesn't match with the path of the file. File seems to be saved in incorrect subject directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-2_bold.json is saved in incorrect subject directory as per sub-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-movielocalizer_run-1_bold.json is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-movielocalizer_run-1_bold.nii.gz is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-movielocalizer_run-1_defacemask.nii.gz is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-movielocalizer_run-1_recording-cardresp_physio.tsv.gz is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_bold.json is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_bold.nii.gz is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_defacemask.nii.gz is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_events.tsv is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-1_recording-cardresp_physio.tsv.gz is saved in incorrect session directory as per ses-id in filename.

Session label in the filename doesn't match with the path of the file. File seems to be saved in incorrect session directory.

File: /eyetracking while movie watching, plus visual localizers/sub-01/ses-localizer/func/sub-01_ses-localizer_task-objectcategories_run-2_bold.json is saved in incorrect session directory as per ses-id in filename.

No BIDS compatible data found for subject 01

No BIDS compatible data found for subject 02

No BIDS compatible data found for subject 03

No BIDS compatible data found for subject 04

No BIDS compatible data found for subject 05

No BIDS compatible data found for subject 06

No BIDS compatible data found for subject 09

No BIDS compatible data found for subject 10

No BIDS compatible data found for subject 14

No BIDS compatible data found for subject 15