Journal article
Cluster failure: Why fMRI inferences for spatial extent have inflated false-positive rates
- Abstract:
- The most widely used task functional magnetic resonance imaging (fMRI) analyses use parametric statistical methods that depend on a variety of assumptions. In this work, we use real resting-state data and a total of 3 million random task group analyses to compute empirical familywise error rates for the fMRI software packages SPM, FSL, and AFNI, as well as a nonparametric permutation method. For a nominal familywise error rate of 5%, the parametric statistical methods are shown to be conservative for voxelwise inference and invalid for clusterwise inference. Our results suggest that the principal cause of the invalid cluster inferences is spatial autocorrelation functions that do not follow the assumed Gaussian shape. By comparison, the nonparametric permutation test is found to produce nominal results for voxelwise as well as clusterwise inference. These findings speak to the need of validating the statistical methods being used in the field of neuroimaging.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 659.6KB, Terms of use)
-
- Publisher copy:
- 10.1073/pnas.1602413113
Authors
- Publisher:
- National Academy of Sciences
- Journal:
- Proceedings of the National Academy of Sciences of the United States of America More from this journal
- Volume:
- 113
- Issue:
- 28
- Pages:
- 7900-7905
- Publication date:
- 2016-06-28
- Acceptance date:
- 2016-05-17
- DOI:
- EISSN:
-
1091-6490
- ISSN:
-
0027-8424
- Pmid:
-
27357684
- Language:
-
English
- Keywords:
- Pubs id:
-
pubs:908847
- UUID:
-
uuid:31bdede9-0985-4308-a860-236750e7ccb9
- Local pid:
-
pubs:908847
- Source identifiers:
-
908847
- Deposit date:
-
2018-11-01
Terms of use
- Copyright holder:
- Eklund et al
- Copyright date:
- 2016
- Notes:
- Freely available online through the PNAS open access option.
If you are the owner of this record, you can report an update to it here: Report update to this record