search

spatialtopology / spacetop-prep

code for transferring data and preprocessing
MIT License
0 stars 3 forks source link

sub-0025 func sbref #5

Closed jungheejung closed 4 months ago

jungheejung commented 3 years ago 
                    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.nii.gz
            ./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_bold.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-0025_ses-03_task-social_acq-mb8_51_run-03_bold.json
            ./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_bold.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-0025_ses-03_task-social_acq-mb8_51_run-03_bold.nii.gz
            ./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_events.tsv
                    Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
                    Evidence: sub-0025_ses-03_task-social_acq-mb8_51_run-03_events.tsv
            ./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.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-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.json
            ./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.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-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.nii.gz

    2: [ERR] acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec. (code: 59 - ACQ_NAME_CONTAIN_ILLEGAL_CHARACTER)
            ./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_bold.json
                    acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
                    Evidence: acq name contains illegal character:/sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_bold.json
            ./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_events.tsv
                    acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
                    Evidence: acq name contains illegal character:/sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_events.tsv
            ./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.nii.gz
                    acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
                    Evidence: acq name contains illegal character:/sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.nii.gz
jungheejung commented 4 months ago

resolved this with heudiconv