sub-0017 fmap naming convention

                    Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
                    Evidence: sub-0016_ses-01_acq-mb8_dir-pa_run=-PVS-run-04_epi.nii.gz
            ./sub-0017/ses-01/fmap/sub-0017_ses-01_acq-mb8_dir-ap_alignvideos_run-02_epi.json
                    Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
                    Evidence: sub-0017_ses-01_acq-mb8_dir-ap_alignvideos_run-02_epi.json
            ./sub-0017/ses-01/fmap/sub-0017_ses-01_acq-mb8_dir-ap_alignvideos_run-02_epi.nii.gz
                    Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
                    Evidence: sub-0017_ses-01_acq-mb8_dir-ap_alignvideos_run-02_epi.nii.gz
            ./sub-0017/ses-01/fmap/sub-0017_ses-01_acq-mb8_dir-pa_alignvideos_run-02_epi.json
                    Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
                    Evidence: sub-0017_ses-01_acq-mb8_dir-pa_alignvideos_run-02_epi.json
            ./sub-0017/ses-01/fmap/sub-0017_ses-01_acq-mb8_dir-pa_alignvideos_run-02_epi.nii.gz
spatialtopology / spacetop-prep

sub-0017 fmap naming convention #4
