Human es-fMRI Resource: Concurrent deep-brain stimulation and whole-brain functional MRI

uploaded by Remya Nair on 2020-05-16 - over 1 year ago
last modified on 2020-08-25 - about 1 year ago
authored by Thompson WH*, Nair R*, Oya H*, Esteban O, Shine JM, Petkov CI, Poldrack RA, Howard M, Adolphs R†, *equally contributing, †corresponding author
251674
Your dataset is no longer valid. You must fix the 1 Error to use all of the site features.

/sub-292/ses-postop/ieeg/sub-292_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-292_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-292/ses-postop/ieeg/sub-292_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-292_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

/sub-294/ses-postop/ieeg/sub-294_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-294_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-294/ses-postop/ieeg/sub-294_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-294_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

/sub-302/ses-postop/ieeg/sub-302_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-302_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-302/ses-postop/ieeg/sub-302_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-302_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

/sub-303/ses-postop/ieeg/sub-303_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-303_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-303/ses-postop/ieeg/sub-303_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-303_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

/sub-307/ses-postop/ieeg/sub-307_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-307_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-307/ses-postop/ieeg/sub-307_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-307_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

and 36 more files

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-01_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-01_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-01_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-01_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-01_bold.json

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-02_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-02_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-02_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-02_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-02_bold.json

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-03_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-03_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-03_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-03_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-03_bold.json

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-04_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-04_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-04_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-04_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-04_bold.json

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-05_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-05_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-05_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-05_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-05_bold.json

/sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-01_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-01_bold.json, /sub-372/sub-372_task-rest_bold.json, /sub-372/sub-372_task-rest_run-01_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_run-01_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-01_bold.json

/sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-02_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-02_bold.json, /sub-372/sub-372_task-rest_bold.json, /sub-372/sub-372_task-rest_run-02_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_run-02_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-02_bold.json

/sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-03_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-03_bold.json, /sub-372/sub-372_task-rest_bold.json, /sub-372/sub-372_task-rest_run-03_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_run-03_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-03_bold.json

/sub-376/ses-preop/func/sub-376_ses-preop_task-rest_run-01_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-01_bold.json, /sub-376/sub-376_task-rest_bold.json, /sub-376/sub-376_task-rest_run-01_bold.json, /sub-376/ses-preop/sub-376_ses-preop_task-rest_bold.json, /sub-376/ses-preop/sub-376_ses-preop_task-rest_run-01_bold.json, /sub-376/ses-preop/func/sub-376_ses-preop_task-rest_bold.json, /sub-376/ses-preop/func/sub-376_ses-preop_task-rest_run-01_bold.json

/sub-376/ses-preop/func/sub-376_ses-preop_task-rest_run-02_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-02_bold.json, /sub-376/sub-376_task-rest_bold.json, /sub-376/sub-376_task-rest_run-02_bold.json, /sub-376/ses-preop/sub-376_ses-preop_task-rest_bold.json, /sub-376/ses-preop/sub-376_ses-preop_task-rest_run-02_bold.json, /sub-376/ses-preop/func/sub-376_ses-preop_task-rest_bold.json, /sub-376/ses-preop/func/sub-376_ses-preop_task-rest_run-02_bold.json

and 19 more files

/sub-294/ses-postop/func/sub-294_ses-postop_task-es_run-02_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-02_events.tsv, /task-es_run-02_events.tsv, /sub-294/sub-294_events.tsv, /sub-294/sub-294_task-es_events.tsv, /sub-294/sub-294_run-02_events.tsv, /sub-294/sub-294_task-es_run-02_events.tsv, /sub-294/ses-postop/sub-294_ses-postop_events.tsv, /sub-294/ses-postop/sub-294_ses-postop_task-es_events.tsv, /sub-294/ses-postop/sub-294_ses-postop_run-02_events.tsv, /sub-294/ses-postop/sub-294_ses-postop_task-es_run-02_events.tsv, /sub-294/ses-postop/func/sub-294_ses-postop_events.tsv, /sub-294/ses-postop/func/sub-294_ses-postop_task-es_events.tsv, /sub-294/ses-postop/func/sub-294_ses-postop_run-02_events.tsv, /sub-294/ses-postop/func/sub-294_ses-postop_task-es_run-02_events.tsv

/sub-303/ses-postop/func/sub-303_ses-postop_task-es_run-06_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-06_events.tsv, /task-es_run-06_events.tsv, /sub-303/sub-303_events.tsv, /sub-303/sub-303_task-es_events.tsv, /sub-303/sub-303_run-06_events.tsv, /sub-303/sub-303_task-es_run-06_events.tsv, /sub-303/ses-postop/sub-303_ses-postop_events.tsv, /sub-303/ses-postop/sub-303_ses-postop_task-es_events.tsv, /sub-303/ses-postop/sub-303_ses-postop_run-06_events.tsv, /sub-303/ses-postop/sub-303_ses-postop_task-es_run-06_events.tsv, /sub-303/ses-postop/func/sub-303_ses-postop_events.tsv, /sub-303/ses-postop/func/sub-303_ses-postop_task-es_events.tsv, /sub-303/ses-postop/func/sub-303_ses-postop_run-06_events.tsv, /sub-303/ses-postop/func/sub-303_ses-postop_task-es_run-06_events.tsv

/sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-02_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-02_events.tsv, /task-es_run-02_events.tsv, /sub-314/sub-314_events.tsv, /sub-314/sub-314_task-es_events.tsv, /sub-314/sub-314_run-02_events.tsv, /sub-314/sub-314_task-es_run-02_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_run-02_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_run-02_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_run-02_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-02_events.tsv

/sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-03_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-03_events.tsv, /task-es_run-03_events.tsv, /sub-314/sub-314_events.tsv, /sub-314/sub-314_task-es_events.tsv, /sub-314/sub-314_run-03_events.tsv, /sub-314/sub-314_task-es_run-03_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_run-03_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_run-03_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_run-03_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-03_events.tsv

/sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-04_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-04_events.tsv, /task-es_run-04_events.tsv, /sub-314/sub-314_events.tsv, /sub-314/sub-314_task-es_events.tsv, /sub-314/sub-314_run-04_events.tsv, /sub-314/sub-314_task-es_run-04_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_run-04_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_run-04_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_run-04_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-04_events.tsv

/sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-05_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-05_events.tsv, /task-es_run-05_events.tsv, /sub-314/sub-314_events.tsv, /sub-314/sub-314_task-es_events.tsv, /sub-314/sub-314_run-05_events.tsv, /sub-314/sub-314_task-es_run-05_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_run-05_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_run-05_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_run-05_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-05_events.tsv

/sub-292/ses-postop/anat/sub-292_ses-postop_T1w.nii

The most common set of dimensions is: 256,224,256 (voxels), This file has the dimensions: 256,240,256 (voxels). The most common resolution is: 0.98mm x 1.00mm x 0.98mm, This file has the resolution: 1.00mm x 1.00mm x 1.00mm.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-01_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-02_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-03_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-04_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-05_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-preop/anat/sub-292_ses-preop_T1w.nii

The most common set of dimensions is: 256,252,256 (voxels), This file has the dimensions: 256,256,256 (voxels).

/sub-292/ses-preop/fmap/sub-292_ses-preop_run-01_magnitude1.nii

The most common set of dimensions is: 64,64,36 (voxels), This file has the dimensions: 64,64,31 (voxels). The most common resolution is: 3.44mm x 3.44mm x 4.00mm, This file has the resolution: 3.44mm x 3.44mm x 4.02mm.

/sub-292/ses-preop/fmap/sub-292_ses-preop_run-01_magnitude2.nii

The most common set of dimensions is: 64,64,36 (voxels), This file has the dimensions: 64,64,31 (voxels). The most common resolution is: 3.44mm x 3.44mm x 4.00mm, This file has the resolution: 3.44mm x 3.44mm x 4.02mm.

/sub-292/ses-preop/fmap/sub-292_ses-preop_run-01_phasediff.nii

The most common set of dimensions is: 64,64,36 (voxels), This file has the dimensions: 64,64,31 (voxels). The most common resolution is: 3.44mm x 3.44mm x 4.00mm, This file has the resolution: 3.44mm x 3.44mm x 4.02mm.

and 235 more files

/participants.tsv

Tabular file contains custom columns not described in a data dictionary

Columns: sex, age, handedness not defined, please define in: /participants.json

/sub-303/ses-postop/func/sub-303_ses-postop_task-es_run-05_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-330/ses-postop/func/sub-330_ses-postop_task-es_run-02_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-331/ses-postop/func/sub-331_ses-postop_task-es_run-04_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-357/ses-postop/func/sub-357_ses-postop_task-es_run-09_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-357/ses-postop/func/sub-357_ses-postop_task-es_run-10_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-01_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-02_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-03_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-04_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-05_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

and 12 more files

OpenNeuro Accession Number: ds002799
Files: 1149, Size: 18.57GB, Subjects: 26, Sessions: 2
Available Tasks: es, rest
Available Modalities: MRI, iEEG

README

Link to published paper for this data resource: https://rdcu.be/b57kz

This collection contains data from 26 human patients who underwent electrical stimulation during functional magnetic resonance imaging (es-fMRI). The patients had medically refractory epilepsy requiring surgically implanted intracranial electrodes in cortical and subcortical locations. One or multiple contacts on these electrodes were stimulated while simultaneously recording BOLD-fMRI activity in a block design. Multiple runs exist for patients with different stimulation sites. Data is organized in two sessions : Pre-op (pre electrode implantation) and Post-op (post electrode implantation). Raw data is provided in BIDS format and consists of T1s, T2s, resting state scans (pre-op), es-fMRI scans(post-op) , any associated field-maps and stimulation electrode coordinates and stimulation parameters. Pre-processed data (fMRIprep and Freesurfer) is present in the ‘derivatives’ folder.

Notes: 1. Subject IDs 339, 369 and 394 do not have stimulation electrode location data available. 2. Electrodes are in chA-chB format (chA gets leading positive phase of the stimulation). This information is stored in the "channel" file for each stimulation run. 3. In some cases, two distant sites were stimulated simultaneously as indicated by the electrode listed under the appropriate run IDs within the ieeg folders.

Authors

  • Thompson WH*
  • Nair R*
  • Oya H*
  • Esteban O
  • Shine JM
  • Petkov CI
  • Poldrack RA
  • Howard M
  • Adolphs R†
  • *equally contributing, †corresponding author

Dataset DOI

10.18112/openneuro.ds002799.v1.0.3

License

CC0

Acknowledgements

How to Acknowledge

Funding

  • Funded by NIH grant U01NS103780 (RP, RA and MH)
  • The Simons Foundation Collaboration on the Global Brain (RA)
  • Knut and Alice Wallenberg Foundation grant 2016.0473 (WHT)
  • UK Wellcome Trust (CIP) and European Research Council (CIP)
  • The OpenNeuro repository is funded by NIH Grant R24MH117179 (RP)

References and Links

Ethics Approvals

How To Cite

Copy
Thompson WH* and Nair R* and Oya H* and Esteban O and Shine JM and Petkov CI and Poldrack RA and Howard M and Adolphs R† and *equally contributing, †corresponding author (2020). Human es-fMRI Resource: Concurrent deep-brain stimulation and whole-brain functional MRI. OpenNeuro. [Dataset] doi: 10.18112/openneuro.ds002799.v1.0.3
More citation info

Human es-fMRI Resource: Concurrent deep-brain stimulation and whole-brain functional MRI

uploaded by Remya Nair on 2020-05-16 - over 1 year ago
last modified on 2020-08-25 - about 1 year ago
authored by Thompson WH*, Nair R*, Oya H*, Esteban O, Shine JM, Petkov CI, Poldrack RA, Howard M, Adolphs R†, *equally contributing, †corresponding author
251674

OpenNeuro Accession Number: ds002799
Files: 1149, Size: 18.57GB, Subjects: 26, Sessions: 2
Available Tasks: es, rest
Available Modalities: MRI, iEEG

README

Link to published paper for this data resource: https://rdcu.be/b57kz

This collection contains data from 26 human patients who underwent electrical stimulation during functional magnetic resonance imaging (es-fMRI). The patients had medically refractory epilepsy requiring surgically implanted intracranial electrodes in cortical and subcortical locations. One or multiple contacts on these electrodes were stimulated while simultaneously recording BOLD-fMRI activity in a block design. Multiple runs exist for patients with different stimulation sites. Data is organized in two sessions : Pre-op (pre electrode implantation) and Post-op (post electrode implantation). Raw data is provided in BIDS format and consists of T1s, T2s, resting state scans (pre-op), es-fMRI scans(post-op) , any associated field-maps and stimulation electrode coordinates and stimulation parameters. Pre-processed data (fMRIprep and Freesurfer) is present in the ‘derivatives’ folder.

Notes: 1. Subject IDs 339, 369 and 394 do not have stimulation electrode location data available. 2. Electrodes are in chA-chB format (chA gets leading positive phase of the stimulation). This information is stored in the "channel" file for each stimulation run. 3. In some cases, two distant sites were stimulated simultaneously as indicated by the electrode listed under the appropriate run IDs within the ieeg folders.

Authors

  • Thompson WH*
  • Nair R*
  • Oya H*
  • Esteban O
  • Shine JM
  • Petkov CI
  • Poldrack RA
  • Howard M
  • Adolphs R†
  • *equally contributing, †corresponding author

Dataset DOI

10.18112/openneuro.ds002799.v1.0.3

License

CC0

Acknowledgements

How to Acknowledge

Funding

  • Funded by NIH grant U01NS103780 (RP, RA and MH)
  • The Simons Foundation Collaboration on the Global Brain (RA)
  • Knut and Alice Wallenberg Foundation grant 2016.0473 (WHT)
  • UK Wellcome Trust (CIP) and European Research Council (CIP)
  • The OpenNeuro repository is funded by NIH Grant R24MH117179 (RP)

References and Links

Ethics Approvals

How To Cite

Copy
Thompson WH* and Nair R* and Oya H* and Esteban O and Shine JM and Petkov CI and Poldrack RA and Howard M and Adolphs R† and *equally contributing, †corresponding author (2020). Human es-fMRI Resource: Concurrent deep-brain stimulation and whole-brain functional MRI. OpenNeuro. [Dataset] doi: 10.18112/openneuro.ds002799.v1.0.3
More citation info

Dataset File Tree

Git Hash: 2e4b903 

BIDS Validation

Your dataset is no longer valid. You must fix the 1 Error to use all of the site features.

/sub-292/ses-postop/ieeg/sub-292_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-292_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-292/ses-postop/ieeg/sub-292_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-292_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

/sub-294/ses-postop/ieeg/sub-294_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-294_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-294/ses-postop/ieeg/sub-294_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-294_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

/sub-302/ses-postop/ieeg/sub-302_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-302_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-302/ses-postop/ieeg/sub-302_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-302_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

/sub-303/ses-postop/ieeg/sub-303_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-303_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-303/ses-postop/ieeg/sub-303_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-303_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

/sub-307/ses-postop/ieeg/sub-307_ses-postop_space-MNI152NLin6Asym_coordsystem.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.

sub-307_ses-postop_space-MNI152NLin6Asym_coordsystem.json

/sub-307/ses-postop/ieeg/sub-307_ses-postop_space-MNI152NLin6Asym_electrodes.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.

sub-307_ses-postop_space-MNI152NLin6Asym_electrodes.tsv

and 36 more files

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-01_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-01_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-01_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-01_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-01_bold.json

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-02_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-02_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-02_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-02_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-02_bold.json

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-03_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-03_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-03_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-03_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-03_bold.json

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-04_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-04_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-04_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-04_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-04_bold.json

/sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-05_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-05_bold.json, /sub-352/sub-352_task-rest_bold.json, /sub-352/sub-352_task-rest_run-05_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/sub-352_ses-preop_task-rest_run-05_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_bold.json, /sub-352/ses-preop/func/sub-352_ses-preop_task-rest_run-05_bold.json

/sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-01_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-01_bold.json, /sub-372/sub-372_task-rest_bold.json, /sub-372/sub-372_task-rest_run-01_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_run-01_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-01_bold.json

/sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-02_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-02_bold.json, /sub-372/sub-372_task-rest_bold.json, /sub-372/sub-372_task-rest_run-02_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_run-02_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-02_bold.json

/sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-03_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-03_bold.json, /sub-372/sub-372_task-rest_bold.json, /sub-372/sub-372_task-rest_run-03_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/sub-372_ses-preop_task-rest_run-03_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_bold.json, /sub-372/ses-preop/func/sub-372_ses-preop_task-rest_run-03_bold.json

/sub-376/ses-preop/func/sub-376_ses-preop_task-rest_run-01_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-01_bold.json, /sub-376/sub-376_task-rest_bold.json, /sub-376/sub-376_task-rest_run-01_bold.json, /sub-376/ses-preop/sub-376_ses-preop_task-rest_bold.json, /sub-376/ses-preop/sub-376_ses-preop_task-rest_run-01_bold.json, /sub-376/ses-preop/func/sub-376_ses-preop_task-rest_bold.json, /sub-376/ses-preop/func/sub-376_ses-preop_task-rest_run-01_bold.json

/sub-376/ses-preop/func/sub-376_ses-preop_task-rest_run-02_bold.nii

You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /task-rest_run-02_bold.json, /sub-376/sub-376_task-rest_bold.json, /sub-376/sub-376_task-rest_run-02_bold.json, /sub-376/ses-preop/sub-376_ses-preop_task-rest_bold.json, /sub-376/ses-preop/sub-376_ses-preop_task-rest_run-02_bold.json, /sub-376/ses-preop/func/sub-376_ses-preop_task-rest_bold.json, /sub-376/ses-preop/func/sub-376_ses-preop_task-rest_run-02_bold.json

and 19 more files

/sub-294/ses-postop/func/sub-294_ses-postop_task-es_run-02_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-02_events.tsv, /task-es_run-02_events.tsv, /sub-294/sub-294_events.tsv, /sub-294/sub-294_task-es_events.tsv, /sub-294/sub-294_run-02_events.tsv, /sub-294/sub-294_task-es_run-02_events.tsv, /sub-294/ses-postop/sub-294_ses-postop_events.tsv, /sub-294/ses-postop/sub-294_ses-postop_task-es_events.tsv, /sub-294/ses-postop/sub-294_ses-postop_run-02_events.tsv, /sub-294/ses-postop/sub-294_ses-postop_task-es_run-02_events.tsv, /sub-294/ses-postop/func/sub-294_ses-postop_events.tsv, /sub-294/ses-postop/func/sub-294_ses-postop_task-es_events.tsv, /sub-294/ses-postop/func/sub-294_ses-postop_run-02_events.tsv, /sub-294/ses-postop/func/sub-294_ses-postop_task-es_run-02_events.tsv

/sub-303/ses-postop/func/sub-303_ses-postop_task-es_run-06_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-06_events.tsv, /task-es_run-06_events.tsv, /sub-303/sub-303_events.tsv, /sub-303/sub-303_task-es_events.tsv, /sub-303/sub-303_run-06_events.tsv, /sub-303/sub-303_task-es_run-06_events.tsv, /sub-303/ses-postop/sub-303_ses-postop_events.tsv, /sub-303/ses-postop/sub-303_ses-postop_task-es_events.tsv, /sub-303/ses-postop/sub-303_ses-postop_run-06_events.tsv, /sub-303/ses-postop/sub-303_ses-postop_task-es_run-06_events.tsv, /sub-303/ses-postop/func/sub-303_ses-postop_events.tsv, /sub-303/ses-postop/func/sub-303_ses-postop_task-es_events.tsv, /sub-303/ses-postop/func/sub-303_ses-postop_run-06_events.tsv, /sub-303/ses-postop/func/sub-303_ses-postop_task-es_run-06_events.tsv

/sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-02_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-02_events.tsv, /task-es_run-02_events.tsv, /sub-314/sub-314_events.tsv, /sub-314/sub-314_task-es_events.tsv, /sub-314/sub-314_run-02_events.tsv, /sub-314/sub-314_task-es_run-02_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_run-02_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_run-02_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_run-02_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-02_events.tsv

/sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-03_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-03_events.tsv, /task-es_run-03_events.tsv, /sub-314/sub-314_events.tsv, /sub-314/sub-314_task-es_events.tsv, /sub-314/sub-314_run-03_events.tsv, /sub-314/sub-314_task-es_run-03_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_run-03_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_run-03_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_run-03_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-03_events.tsv

/sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-04_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-04_events.tsv, /task-es_run-04_events.tsv, /sub-314/sub-314_events.tsv, /sub-314/sub-314_task-es_events.tsv, /sub-314/sub-314_run-04_events.tsv, /sub-314/sub-314_task-es_run-04_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_run-04_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_run-04_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_run-04_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-04_events.tsv

/sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-05_bold.nii

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-es_events.tsv, /run-05_events.tsv, /task-es_run-05_events.tsv, /sub-314/sub-314_events.tsv, /sub-314/sub-314_task-es_events.tsv, /sub-314/sub-314_run-05_events.tsv, /sub-314/sub-314_task-es_run-05_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_run-05_events.tsv, /sub-314/ses-postop/sub-314_ses-postop_task-es_run-05_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_run-05_events.tsv, /sub-314/ses-postop/func/sub-314_ses-postop_task-es_run-05_events.tsv

/sub-292/ses-postop/anat/sub-292_ses-postop_T1w.nii

The most common set of dimensions is: 256,224,256 (voxels), This file has the dimensions: 256,240,256 (voxels). The most common resolution is: 0.98mm x 1.00mm x 0.98mm, This file has the resolution: 1.00mm x 1.00mm x 1.00mm.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-01_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-02_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-03_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-04_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-postop/func/sub-292_ses-postop_task-es_run-05_bold.nii

The most common set of dimensions is: 68,68,44,221 (voxels), This file has the dimensions: 68,68,46,254 (voxels). The most common resolution is: 3.24mm x 3.24mm x 3.00mm x 3.00s, This file has the resolution: 3.24mm x 3.24mm x 3.00mm x 3.10s.

/sub-292/ses-preop/anat/sub-292_ses-preop_T1w.nii

The most common set of dimensions is: 256,252,256 (voxels), This file has the dimensions: 256,256,256 (voxels).

/sub-292/ses-preop/fmap/sub-292_ses-preop_run-01_magnitude1.nii

The most common set of dimensions is: 64,64,36 (voxels), This file has the dimensions: 64,64,31 (voxels). The most common resolution is: 3.44mm x 3.44mm x 4.00mm, This file has the resolution: 3.44mm x 3.44mm x 4.02mm.

/sub-292/ses-preop/fmap/sub-292_ses-preop_run-01_magnitude2.nii

The most common set of dimensions is: 64,64,36 (voxels), This file has the dimensions: 64,64,31 (voxels). The most common resolution is: 3.44mm x 3.44mm x 4.00mm, This file has the resolution: 3.44mm x 3.44mm x 4.02mm.

/sub-292/ses-preop/fmap/sub-292_ses-preop_run-01_phasediff.nii

The most common set of dimensions is: 64,64,36 (voxels), This file has the dimensions: 64,64,31 (voxels). The most common resolution is: 3.44mm x 3.44mm x 4.00mm, This file has the resolution: 3.44mm x 3.44mm x 4.02mm.

and 235 more files

/participants.tsv

Tabular file contains custom columns not described in a data dictionary

Columns: sex, age, handedness not defined, please define in: /participants.json

/sub-303/ses-postop/func/sub-303_ses-postop_task-es_run-05_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-330/ses-postop/func/sub-330_ses-postop_task-es_run-02_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-331/ses-postop/func/sub-331_ses-postop_task-es_run-04_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-357/ses-postop/func/sub-357_ses-postop_task-es_run-09_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-357/ses-postop/func/sub-357_ses-postop_task-es_run-10_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-01_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-02_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-03_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-04_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

/sub-376/ses-postop/func/sub-376_ses-postop_task-es_run-05_events.tsv

The onset of the last event is after the total duration of the corresponding scan. This design is suspiciously long.

and 12 more files

Dataset File Tree

Git Hash: 2e4b903 

Comments

Please sign in to contribute to the discussion.