Location:		bids/sub-4008/ses-ofM/func/sub-4008_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
	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. 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-4008_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_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. 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-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.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. 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-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4008_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.json
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_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. 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-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.json

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.nii
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.nii
	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. 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-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.nii

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.json
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.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. 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-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.json

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.nii
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.nii
	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. 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-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.nii

	Type:		Error
	File:		sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_events.tsv
	Location:		bids/sub-4008/ses-ofMaF/func/sub-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_events.tsv
	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. 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-4008_ses-ofMaF_acq-EPIlowcov_trial-JogB_events.tsv

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_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. 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-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.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. 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-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4008_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.json
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_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. 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-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.json

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.nii
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.nii
	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. 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-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.nii

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.json
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.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. 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-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.json

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.nii
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.nii
	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. 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-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.nii

	Type:		Error
	File:		sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_events.tsv
	Location:		bids/sub-4008/ses-ofMcF1/func/sub-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_events.tsv
	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. 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-4008_ses-ofMcF1_acq-EPIlowcov_trial-JogB_events.tsv

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_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. 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-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.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. 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-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4008_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.json
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_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. 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-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.json

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.nii
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.nii
	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. 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-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.nii

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.json
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.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. 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-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.json

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.nii
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.nii
	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. 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-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.nii

	Type:		Error
	File:		sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_events.tsv
	Location:		bids/sub-4008/ses-ofMcF2/func/sub-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_events.tsv
	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. 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-4008_ses-ofMcF2_acq-EPIlowcov_trial-JogB_events.tsv

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_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. 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-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.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. 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-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4008_ses-ofMpF_acq-EPIlowcov_task-JogB_events.tsv

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_bold.json
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_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. 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-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_bold.json

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_bold.nii
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_bold.nii
	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. 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-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_bold.nii

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_cbv.json
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_cbv.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. 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-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_cbv.json

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_cbv.nii
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_cbv.nii
	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. 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-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_cbv.nii

	Type:		Error
	File:		sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_events.tsv
	Location:		bids/sub-4008/ses-ofMpF/func/sub-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_events.tsv
	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. 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-4008_ses-ofMpF_acq-EPIlowcov_trial-JogB_events.tsv

	Type:		Error
	File:		sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4009/ses-ofM/func/sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_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. 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-4009_ses-ofM_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4009/ses-ofM/func/sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4009_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4009/ses-ofM/func/sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_cbv.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. 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-4009_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4009/ses-ofM/func/sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4009_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4009/ses-ofM/func/sub-4009_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4009_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv

	Type:		Error
	File:		sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4009/ses-ofMaF/func/sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_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. 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-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4009/ses-ofMaF/func/sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4009/ses-ofMaF/func/sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.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. 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-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4009/ses-ofMaF/func/sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4009/ses-ofMaF/func/sub-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4009_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv

	Type:		Error
	File:		sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4009/ses-ofMcF1/func/sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_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. 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-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4009/ses-ofMcF1/func/sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4009/ses-ofMcF1/func/sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.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. 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-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4009/ses-ofMcF1/func/sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4009/ses-ofMcF1/func/sub-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4009_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv

	Type:		Error
	File:		sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4009/ses-ofMcF2/func/sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_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. 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-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4009/ses-ofMcF2/func/sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4009/ses-ofMcF2/func/sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.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. 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-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4009/ses-ofMcF2/func/sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4009/ses-ofMcF2/func/sub-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4009_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv

	Type:		Error
	File:		sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.json
	Location:		bids/sub-4009/ses-ofMpF/func/sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_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. 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-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.json

	Type:		Error
	File:		sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.nii
	Location:		bids/sub-4009/ses-ofMpF/func/sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.nii
	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. 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-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_bold.nii

	Type:		Error
	File:		sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.json
	Location:		bids/sub-4009/ses-ofMpF/func/sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.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. 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-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.json

	Type:		Error
	File:		sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.nii
	Location:		bids/sub-4009/ses-ofMpF/func/sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.nii
	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. 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-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_cbv.nii

	Type:		Error
	File:		sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_events.tsv
	Location:		bids/sub-4009/ses-ofMpF/func/sub-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_events.tsv
	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. 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-4009_ses-ofMpF_acq-EPIlowcov_task-JogB_events.tsv

======================================================

File Path: The compulsory file /dataset_description.json is missing. See Section 8.1 of the BIDS specification.

	Type:		Error

======================================================

File Path: 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.

	Type:		Warning
	File:		sub-4001_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4001/ses-ofMpF/anat/sub-4001_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4001, but is present for most other subjects.
	Type:		Warning
	File:		sub-4001_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4001/ses-ofMpF/anat/sub-4001_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4001, but is present for most other subjects.
	Type:		Warning
	File:		sub-4001_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4001/ses-ofMr1/anat/sub-4001_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4001, but is present for most other subjects.
	Type:		Warning
	File:		sub-4001_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4001/ses-ofMr1/anat/sub-4001_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4001, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMaF_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4002/ses-ofMaF/anat/sub-4002_ses-ofMaF_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMaF_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4002/ses-ofMaF/anat/sub-4002_ses-ofMaF_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMcF1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4002/ses-ofMcF1/anat/sub-4002_ses-ofMcF1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMcF1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4002/ses-ofMcF1/anat/sub-4002_ses-ofMcF1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMcF2_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4002/ses-ofMcF2/anat/sub-4002_ses-ofMcF2_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMcF2_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4002/ses-ofMcF2/anat/sub-4002_ses-ofMcF2_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4002/ses-ofMpF/anat/sub-4002_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4002/ses-ofMpF/anat/sub-4002_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4002/ses-ofMr1/anat/sub-4002_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4002_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4002/ses-ofMr1/anat/sub-4002_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4002, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMaF_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4004/ses-ofMaF/anat/sub-4004_ses-ofMaF_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMaF_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4004/ses-ofMaF/anat/sub-4004_ses-ofMaF_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMcF1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4004/ses-ofMcF1/anat/sub-4004_ses-ofMcF1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMcF1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4004/ses-ofMcF1/anat/sub-4004_ses-ofMcF1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMcF2_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4004/ses-ofMcF2/anat/sub-4004_ses-ofMcF2_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMcF2_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4004/ses-ofMcF2/anat/sub-4004_ses-ofMcF2_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4004/ses-ofMpF/anat/sub-4004_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4004/ses-ofMpF/anat/sub-4004_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4004/ses-ofMr1/anat/sub-4004_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4004_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4004/ses-ofMr1/anat/sub-4004_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4004, but is present for most other subjects.
	Type:		Warning
	File:		sub-4005_ses-ofMcF1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4005/ses-ofMcF1/anat/sub-4005_ses-ofMcF1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4005, but is present for most other subjects.
	Type:		Warning
	File:		sub-4005_ses-ofMcF1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4005/ses-ofMcF1/anat/sub-4005_ses-ofMcF1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4005, but is present for most other subjects.
	Type:		Warning
	File:		sub-4005_ses-ofMcF2_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4005/ses-ofMcF2/anat/sub-4005_ses-ofMcF2_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4005, but is present for most other subjects.
	Type:		Warning
	File:		sub-4005_ses-ofMcF2_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4005/ses-ofMcF2/anat/sub-4005_ses-ofMcF2_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4005, but is present for most other subjects.
	Type:		Warning
	File:		sub-4005_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4005/ses-ofMpF/anat/sub-4005_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4005, but is present for most other subjects.
	Type:		Warning
	File:		sub-4005_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4005/ses-ofMpF/anat/sub-4005_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4005, but is present for most other subjects.
	Type:		Warning
	File:		sub-4005_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4005/ses-ofMr1/anat/sub-4005_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4005, but is present for most other subjects.
	Type:		Warning
	File:		sub-4005_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4005/ses-ofMr1/anat/sub-4005_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4005, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofM_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4006/ses-ofM/anat/sub-4006_ses-ofM_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofM_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4006/ses-ofM/anat/sub-4006_ses-ofM_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofMaF_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4006/ses-ofMaF/anat/sub-4006_ses-ofMaF_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofMaF_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4006/ses-ofMaF/anat/sub-4006_ses-ofMaF_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofMcF1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4006/ses-ofMcF1/anat/sub-4006_ses-ofMcF1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofMcF1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4006/ses-ofMcF1/anat/sub-4006_ses-ofMcF1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofMcF2_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4006/ses-ofMcF2/anat/sub-4006_ses-ofMcF2_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofMcF2_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4006/ses-ofMcF2/anat/sub-4006_ses-ofMcF2_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4006/ses-ofMpF/anat/sub-4006_ses-ofMpF_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4006_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4006/ses-ofMpF/anat/sub-4006_ses-ofMpF_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4006, but is present for most other subjects.
	Type:		Warning
	File:		sub-4007_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4007/ses-ofMr1/anat/sub-4007_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4007, but is present for most other subjects.
	Type:		Warning
	File:		sub-4007_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4007/ses-ofMr1/anat/sub-4007_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4007, but is present for most other subjects.
	Type:		Warning
	File:		sub-4008_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4008/ses-ofMr1/anat/sub-4008_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4008, but is present for most other subjects.
	Type:		Warning
	File:		sub-4008_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4008/ses-ofMr1/anat/sub-4008_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4008, but is present for most other subjects.
	Type:		Warning
	File:		sub-4009_ses-ofM_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4009/ses-ofM/anat/sub-4009_ses-ofM_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4009, but is present for most other subjects.
	Type:		Warning
	File:		sub-4009_ses-ofM_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4009/ses-ofM/anat/sub-4009_ses-ofM_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4009, but is present for most other subjects.
	Type:		Warning
	File:		sub-4009_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Location:		/sub-4009/ses-ofMr1/anat/sub-4009_ses-ofMr1_acq-TurboRARElowcov_T2w.json
	Reason:		This file is missing for subject sub-4009, but is present for most other subjects.
	Type:		Warning
	File:		sub-4009_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Location:		/sub-4009/ses-ofMr1/anat/sub-4009_ses-ofMr1_acq-TurboRARElowcov_T2w.nii
	Reason:		This file is missing for subject sub-4009, but is present for most other subjects.

======================================================

task goes before acq, trial is not a valid keyword (try run with numeric
label).
Full pattern template:
sub-<participant_label>[_ses-<session_label>]_task-<task_label>[_acq-][_rec-][_run-]
[_echo-]_bold.nii[.gz]
Best,
Chris
PS Apologies for brevity and potential typos. This message was composed on
a phone.
On Mar 2, 2018 5:00 AM, "Horea Christian"<EMAIL_ADDRESS>wrote:

I'm having trouble validating a dataset, getting errors regarding my
naming (I am aware of the master JSON missing, that's easy to address).
Can you help me out?
I'm pretty sure this conforms quite accurately to BIDS, the only issue
might be that the _cbv modality is not currently covered, but I am
getting errors well in excess of that. Weird.
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. 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-4001_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_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. 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-4001_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
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. 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-4001_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_cbv.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. 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-4001_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
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. 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-4001_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
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. 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-4001_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_bold.json
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_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. 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-4001_ses-ofM_acq-EPIlowcov_trial-JogB_bold.json
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
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. 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-4001_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.json
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.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. 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-4001_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.json
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
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. 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-4001_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
Type:		Error
File:		sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
Location:		bids/sub-4001/ses-ofM/func/sub-4001_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
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. 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-4001_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.json
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_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. 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-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.json
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii
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. 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-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_bold.nii
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.json
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.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. 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-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.json
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii
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. 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-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_cbv.nii
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv
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. 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-4001_ses-ofMaF_acq-EPIlowcov_task-JogB_events.tsv
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.json
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_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. 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-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.json
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.nii
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.nii
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. 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-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_bold.nii
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.json
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.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. 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-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.json
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.nii
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.nii
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. 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-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_cbv.nii
Type:		Error
File:		sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_events.tsv
Location:		bids/sub-4001/ses-ofMaF/func/sub-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_events.tsv
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. 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-4001_ses-ofMaF_acq-EPIlowcov_trial-JogB_events.tsv
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.json
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_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. 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-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.json
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii
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. 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-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_bold.nii
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.json
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.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. 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-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.json
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii
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. 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-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_cbv.nii
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv
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. 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-4001_ses-ofMcF1_acq-EPIlowcov_task-JogB_events.tsv
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.json
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_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. 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-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.json
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.nii
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.nii
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. 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-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_bold.nii
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.json
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.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. 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-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.json
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.nii
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.nii
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. 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-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_cbv.nii
Type:		Error
File:		sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_events.tsv
Location:		bids/sub-4001/ses-ofMcF1/func/sub-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_events.tsv
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. 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-4001_ses-ofMcF1_acq-EPIlowcov_trial-JogB_events.tsv
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.json
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_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. 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-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.json
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii
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. 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-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_bold.nii
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.json
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.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. 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-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.json
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii
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. 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-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_cbv.nii
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv
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. 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-4001_ses-ofMcF2_acq-EPIlowcov_task-JogB_events.tsv
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.json
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_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. 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-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.json
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.nii
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.nii
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. 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-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_bold.nii
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.json
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.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. 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-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.json
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.nii
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.nii
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. 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-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_cbv.nii
Type:		Error
File:		sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_events.tsv
Location:		bids/sub-4001/ses-ofMcF2/func/sub-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_events.tsv
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. 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-4001_ses-ofMcF2_acq-EPIlowcov_trial-JogB_events.tsv
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_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. 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-4002_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
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. 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-4002_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_cbv.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. 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-4002_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
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. 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-4002_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
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. 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-4002_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_bold.json
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_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. 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-4002_ses-ofM_acq-EPIlowcov_trial-JogB_bold.json
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
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. 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-4002_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.json
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.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. 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-4002_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.json
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
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. 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-4002_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
Type:		Error
File:		sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
Location:		bids/sub-4002/ses-ofM/func/sub-4002_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
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. 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-4002_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_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. 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-4004_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
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. 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-4004_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_cbv.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. 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-4004_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
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. 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-4004_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
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. 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-4004_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_bold.json
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_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. 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-4004_ses-ofM_acq-EPIlowcov_trial-JogB_bold.json
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
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. 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-4004_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.json
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.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. 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-4004_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.json
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
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. 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-4004_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.nii
Type:		Error
File:		sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
Location:		bids/sub-4004/ses-ofM/func/sub-4004_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
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. 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-4004_ses-ofM_acq-EPIlowcov_trial-JogB_events.tsv
Type:		Error
File:		sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
Location:		bids/sub-4005/ses-ofM/func/sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_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. 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-4005_ses-ofM_acq-EPIlowcov_task-JogB_bold.json
Type:		Error
File:		sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
Location:		bids/sub-4005/ses-ofM/func/sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
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. 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-4005_ses-ofM_acq-EPIlowcov_task-JogB_bold.nii
Type:		Error
File:		sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
Location:		bids/sub-4005/ses-ofM/func/sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_cbv.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. 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-4005_ses-ofM_acq-EPIlowcov_task-JogB_cbv.json
Type:		Error
File:		sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
Location:		bids/sub-4005/ses-ofM/func/sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
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. 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-4005_ses-ofM_acq-EPIlowcov_task-JogB_cbv.nii
Type:		Error
File:		sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
Location:		bids/sub-4005/ses-ofM/func/sub-4005_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
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. 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-4005_ses-ofM_acq-EPIlowcov_task-JogB_events.tsv
Type:		Error
File:		sub-4005_ses-ofM_acq-EPIlowcov_trial-JogB_bold.json
Location:		bids/sub-4005/ses-ofM/func/sub-4005_ses-ofM_acq-EPIlowcov_trial-JogB_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. 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-4005_ses-ofM_acq-EPIlowcov_trial-JogB_bold.json
Type:		Error
File:		sub-4005_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
Location:		bids/sub-4005/ses-ofM/func/sub-4005_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
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. 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-4005_ses-ofM_acq-EPIlowcov_trial-JogB_bold.nii
Type:		Error
File:		sub-4005_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.json
Location:		bids/sub-4005/ses-ofM/func/sub-4005_ses-ofM_acq-EPIlowcov_trial-JogB_cbv.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. 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.