Unnamed Dataset

uploaded by William James on 2017-09-24 - over 3 years ago
last modified on 2018-07-17 - almost 3 years ago
19235046
We found 3 Warnings in your dataset. You are not required to fix warnings, but doing so will make your dataset more BIDS compliant.

/sub-001/func/sub-001_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-001/sub-001_bold.json, /sub-001/sub-001_task-rest_bold.json, /sub-001/func/sub-001_task-rest_run-1_bold.json

/sub-002/func/sub-002_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-002/sub-002_bold.json, /sub-002/sub-002_task-rest_bold.json, /sub-002/func/sub-002_task-rest_run-1_bold.json

/sub-003/func/sub-003_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-003/sub-003_bold.json, /sub-003/sub-003_task-rest_bold.json, /sub-003/func/sub-003_task-rest_run-1_bold.json

/sub-004/func/sub-004_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-004/sub-004_bold.json, /sub-004/sub-004_task-rest_bold.json, /sub-004/func/sub-004_task-rest_run-1_bold.json

/sub-005/func/sub-005_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-005/sub-005_bold.json, /sub-005/sub-005_task-rest_bold.json, /sub-005/func/sub-005_task-rest_run-1_bold.json

/sub-006/func/sub-006_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-006/sub-006_bold.json, /sub-006/sub-006_task-rest_bold.json, /sub-006/func/sub-006_task-rest_run-1_bold.json

/sub-007/func/sub-007_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-007/sub-007_bold.json, /sub-007/sub-007_task-rest_bold.json, /sub-007/func/sub-007_task-rest_run-1_bold.json

/sub-008/func/sub-008_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-008/sub-008_bold.json, /sub-008/sub-008_task-rest_bold.json, /sub-008/func/sub-008_task-rest_run-1_bold.json

/sub-009/func/sub-009_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-009/sub-009_bold.json, /sub-009/sub-009_task-rest_bold.json, /sub-009/func/sub-009_task-rest_run-1_bold.json

/sub-010/func/sub-010_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-010/sub-010_bold.json, /sub-010/sub-010_task-rest_bold.json, /sub-010/func/sub-010_task-rest_run-1_bold.json

and 193 more files

/sub-001/func/sub-001_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-001, but is present for at least one other subject.

/sub-002/func/sub-002_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-002, but is present for at least one other subject.

/sub-003/func/sub-003_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-003, but is present for at least one other subject.

/sub-004/func/sub-004_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-004, but is present for at least one other subject.

/sub-005/func/sub-005_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-005, but is present for at least one other subject.

/sub-006/func/sub-006_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-006, but is present for at least one other subject.

/sub-007/func/sub-007_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-007, but is present for at least one other subject.

/sub-008/func/sub-008_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-008, but is present for at least one other subject.

/sub-009/func/sub-009_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-009, but is present for at least one other subject.

/sub-010/func/sub-010_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-010, but is present for at least one other subject.

and 27 more files

/sub-001/anat/sub-001_T1w.nii.gz

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

/sub-001/func/sub-001_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,480 (voxels).

/sub-002/anat/sub-002_T1w.nii.gz

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

/sub-002/func/sub-002_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,360 (voxels).

/sub-003/anat/sub-003_T1w.nii.gz

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

/sub-003/func/sub-003_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,360 (voxels).

/sub-004/anat/sub-004_T1w.nii.gz

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

/sub-004/func/sub-004_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,240 (voxels).

/sub-005/anat/sub-005_T1w.nii.gz

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

/sub-005/func/sub-005_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,240 (voxels).

and 142 more files

OpenNeuro Accession Number: ds000243
Files: 4939, Size: 2.39GB, Subjects: 120, Session: 1
Available Tasks: rest
Available Modalities: T1w, bold

README

These 120 MRI datasets are being released to the public along as part of the materials for “Temporal interpolation alters motion in fMRI scans: magnitudes and consequences for artifact detection” by Power et al. in PLOS ONE.

Included for each subject is a T1-weighted anatomical image (MP-RAGE) and one or more T2*-weighted scans (resting state BOLD scans)

All subjects - were “typical” young adults that reported no significant neurological or psychiatric history - were right-handed and reported that English was their first language - were scanned at Washington University in Saint Louis on a Siemens MAGNETOM Tim Trio 3T scanner with a Siemens 12-channel head coil - were scanned using interleaved ascending product sequences for T2* data - were scanned in the eyes-open resting state fixating a white crosshair on a black background

The data have been described in multiple publications from the Petersen/Schlaggar group, - beginning with Power et al., 2013 “Evidence for hubs in human brain networks” in Neuron - and most comprehensively in Power et al., 2014 “Methods to detect, characterize, and remove motion artifact in resting state fMRI” in Neuroimage - as well as several other publications - see these publications for further details on acquisitions and demographics

Becky Coalson of the Petersen/Schlaggar group collated these scans and de-identified them for public release - the accompanying file “WU120subjectinformation.txt” contains for each subject - the release subject number (1-120) - the same number used in the present publication - the subject number used in Power et al., 2014 - see the WU120SupplememtalCohort_Illustration.pdf from Power et al., 2014 - the subject number to publicly reference the subject - for question/communication purposes with Becky or the Petersen/Schlaggar group - the owner/contributor of the data - age of subject at scanning - sex - handedness - English only speaker - paradigm of the resting state scans - total scan time in resting state - number of rest runs - number of volumes per run - TR of the runs - scanner used (Siemens Tim Trio was in bay3) - slice order (AFNI convention); sequences were ascending interleaved

If there are questions about the scans, please contact Becky Coalson (becky@npg.wustl.edu) or contact the Petersen/Schlaggar group via their website.

JDP 12/23/15

### Comments added by Openfmri Curators ###

General Comments

Defacing -------- Pydeface was used on all anatomical images to ensure deindentification of subjects. The code can be found at https://github.com/poldracklab/pydeface

Quality Control --------------- Mriqc was run on the dataset. Results are located in derivatives/mriqc. Learn more about it here: https://mriqc.readthedocs.io/en/latest/

Where to discuss the dataset ---------------------------- 1) www.openfmri.org/dataset/ds000243/ See the comments section at the bottom of the dataset page. 2) www.neurostars.org Please tag any discussion topics with the tags openfmri and ds000243. 3) Send an email to submissions@openfmri.org. Please include the accession number in your email.

Known Issues ------------ - As per one of the published paper explaining the dataset, its is noted that 2 subjects out of all have different TR for functional runs. However, when checked with submitter, they confirmed that all subjects data shared here have same TR.

Authors

Dataset DOI

Create a new snapshot to obtain a DOI for the snapshot.

License

Acknowledgements

How to Acknowledge

Funding

References and Links

Ethics Approvals

How To Cite

Copy
NO AUTHORS FOUND (2018). Unnamed Dataset. OpenNeuro. [Dataset] doi: null
More citation info

Unnamed Dataset

uploaded by William James on 2017-09-24 - over 3 years ago
last modified on 2018-07-17 - almost 3 years ago
19235046

OpenNeuro Accession Number: ds000243
Files: 4939, Size: 2.39GB, Subjects: 120, Session: 1
Available Tasks: rest
Available Modalities: T1w, bold

README

These 120 MRI datasets are being released to the public along as part of the materials for “Temporal interpolation alters motion in fMRI scans: magnitudes and consequences for artifact detection” by Power et al. in PLOS ONE.

Included for each subject is a T1-weighted anatomical image (MP-RAGE) and one or more T2*-weighted scans (resting state BOLD scans)

All subjects - were “typical” young adults that reported no significant neurological or psychiatric history - were right-handed and reported that English was their first language - were scanned at Washington University in Saint Louis on a Siemens MAGNETOM Tim Trio 3T scanner with a Siemens 12-channel head coil - were scanned using interleaved ascending product sequences for T2* data - were scanned in the eyes-open resting state fixating a white crosshair on a black background

The data have been described in multiple publications from the Petersen/Schlaggar group, - beginning with Power et al., 2013 “Evidence for hubs in human brain networks” in Neuron - and most comprehensively in Power et al., 2014 “Methods to detect, characterize, and remove motion artifact in resting state fMRI” in Neuroimage - as well as several other publications - see these publications for further details on acquisitions and demographics

Becky Coalson of the Petersen/Schlaggar group collated these scans and de-identified them for public release - the accompanying file “WU120subjectinformation.txt” contains for each subject - the release subject number (1-120) - the same number used in the present publication - the subject number used in Power et al., 2014 - see the WU120SupplememtalCohort_Illustration.pdf from Power et al., 2014 - the subject number to publicly reference the subject - for question/communication purposes with Becky or the Petersen/Schlaggar group - the owner/contributor of the data - age of subject at scanning - sex - handedness - English only speaker - paradigm of the resting state scans - total scan time in resting state - number of rest runs - number of volumes per run - TR of the runs - scanner used (Siemens Tim Trio was in bay3) - slice order (AFNI convention); sequences were ascending interleaved

If there are questions about the scans, please contact Becky Coalson (becky@npg.wustl.edu) or contact the Petersen/Schlaggar group via their website.

JDP 12/23/15

### Comments added by Openfmri Curators ###

General Comments

Defacing -------- Pydeface was used on all anatomical images to ensure deindentification of subjects. The code can be found at https://github.com/poldracklab/pydeface

Quality Control --------------- Mriqc was run on the dataset. Results are located in derivatives/mriqc. Learn more about it here: https://mriqc.readthedocs.io/en/latest/

Where to discuss the dataset ---------------------------- 1) www.openfmri.org/dataset/ds000243/ See the comments section at the bottom of the dataset page. 2) www.neurostars.org Please tag any discussion topics with the tags openfmri and ds000243. 3) Send an email to submissions@openfmri.org. Please include the accession number in your email.

Known Issues ------------ - As per one of the published paper explaining the dataset, its is noted that 2 subjects out of all have different TR for functional runs. However, when checked with submitter, they confirmed that all subjects data shared here have same TR.

Authors

Dataset DOI

Create a new snapshot to obtain a DOI for the snapshot.

License

Acknowledgements

How to Acknowledge

Funding

References and Links

Ethics Approvals

How To Cite

Copy
NO AUTHORS FOUND (2018). Unnamed Dataset. OpenNeuro. [Dataset] doi: null
More citation info

Dataset File Tree

Git Hash: 97cf9e3 

BIDS Validation

We found 3 Warnings in your dataset. You are not required to fix warnings, but doing so will make your dataset more BIDS compliant.

/sub-001/func/sub-001_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-001/sub-001_bold.json, /sub-001/sub-001_task-rest_bold.json, /sub-001/func/sub-001_task-rest_run-1_bold.json

/sub-002/func/sub-002_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-002/sub-002_bold.json, /sub-002/sub-002_task-rest_bold.json, /sub-002/func/sub-002_task-rest_run-1_bold.json

/sub-003/func/sub-003_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-003/sub-003_bold.json, /sub-003/sub-003_task-rest_bold.json, /sub-003/func/sub-003_task-rest_run-1_bold.json

/sub-004/func/sub-004_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-004/sub-004_bold.json, /sub-004/sub-004_task-rest_bold.json, /sub-004/func/sub-004_task-rest_run-1_bold.json

/sub-005/func/sub-005_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-005/sub-005_bold.json, /sub-005/sub-005_task-rest_bold.json, /sub-005/func/sub-005_task-rest_run-1_bold.json

/sub-006/func/sub-006_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-006/sub-006_bold.json, /sub-006/sub-006_task-rest_bold.json, /sub-006/func/sub-006_task-rest_run-1_bold.json

/sub-007/func/sub-007_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-007/sub-007_bold.json, /sub-007/sub-007_task-rest_bold.json, /sub-007/func/sub-007_task-rest_run-1_bold.json

/sub-008/func/sub-008_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-008/sub-008_bold.json, /sub-008/sub-008_task-rest_bold.json, /sub-008/func/sub-008_task-rest_run-1_bold.json

/sub-009/func/sub-009_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-009/sub-009_bold.json, /sub-009/sub-009_task-rest_bold.json, /sub-009/func/sub-009_task-rest_run-1_bold.json

/sub-010/func/sub-010_task-rest_run-1_bold.nii.gz

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: /bold.json, /task-rest_bold.json, /sub-010/sub-010_bold.json, /sub-010/sub-010_task-rest_bold.json, /sub-010/func/sub-010_task-rest_run-1_bold.json

and 193 more files

/sub-001/func/sub-001_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-001, but is present for at least one other subject.

/sub-002/func/sub-002_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-002, but is present for at least one other subject.

/sub-003/func/sub-003_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-003, but is present for at least one other subject.

/sub-004/func/sub-004_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-004, but is present for at least one other subject.

/sub-005/func/sub-005_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-005, but is present for at least one other subject.

/sub-006/func/sub-006_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-006, but is present for at least one other subject.

/sub-007/func/sub-007_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-007, but is present for at least one other subject.

/sub-008/func/sub-008_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-008, but is present for at least one other subject.

/sub-009/func/sub-009_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-009, but is present for at least one other subject.

/sub-010/func/sub-010_task-rest_run-2_bold.nii.gz

This file is missing for subject sub-010, but is present for at least one other subject.

and 27 more files

/sub-001/anat/sub-001_T1w.nii.gz

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

/sub-001/func/sub-001_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,480 (voxels).

/sub-002/anat/sub-002_T1w.nii.gz

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

/sub-002/func/sub-002_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,360 (voxels).

/sub-003/anat/sub-003_T1w.nii.gz

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

/sub-003/func/sub-003_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,360 (voxels).

/sub-004/anat/sub-004_T1w.nii.gz

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

/sub-004/func/sub-004_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,240 (voxels).

/sub-005/anat/sub-005_T1w.nii.gz

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

/sub-005/func/sub-005_task-rest_run-1_bold.nii.gz

The most common set of dimensions is: 64,64,32,132 (voxels), This file has the dimensions: 64,64,32,240 (voxels).

and 142 more files

Dataset File Tree

Git Hash: 97cf9e3 

Comments

Please sign in to contribute to the discussion.