Abstract
One important goal of cognitive neuroscience is to discover and explain properties common to all human brains. The traditional solution for comparing functional activations across brains in fMRI is to align each individual brain to a template brain in a Cartesian coordinate system (e.g., the Montreal Neurological Institute template). However, inter-individual anatomical variability leads to decreases in sensitivity (ability to detect a significant activation when it is present) and functional resolution (ability to discriminate spatially adjacent but functionally different neural responses) in group analyses. Subject-specific functional localizers have been previously argued to increase the sensitivity and functional resolution of fMRI analyses in the presence of inter-subject variability in the locations of functional activations (e.g., Brett et al., 2002; Fedorenko and Kanwisher, 2009, 2011; Fedorenko et al., 2010; Kanwisher et al., 1997; Saxe et al., 2006). In the current paper we quantify this dependence of sensitivity and functional resolution on functional variability across subjects in order to illustrate the highly detrimental effects of this variability on traditional group analyses. We show that analyses that use subject-specific functional localizers usually outperform traditional group-based methods in both sensitivity and functional resolution, even when the same total amount of data is used for each analysis. We further discuss how the subject-specific functional localization approach, which has traditionally only been considered in the context of ROI-based analyses, can be extended to whole-brain voxel-based analyses. We conclude that subject-specific functional localizers are particularly well suited for investigating questions of functional specialization in the brain. An SPM toolbox that can perform all of the analyses described in this paper is publicly available, and the analyses can be applied retroactively to any dataset, provided that multiple runs were acquired per subject, even if no explicit "localizer" task was included.