Choosing Stimuli Wisely by Using Individual Differences: A Step-by-Step Tutorial for the One-Stimulus-Per-Factor Principle in Vision Science and Optometric Assessment
Given that data collection time in vision research and clinical assessment is limited, investigators and clinicians must select stimuli that maximize diagnostic information with minimum redundancy. This article proposes that analyzing individual differences—through factor analysis (FA), principal component analysis (PCA), and multidimensional scaling (MDS)—offers a principled approach. The covariance structure of individual variation reveals the minimum number of independent factors underlying a visual function, and therefore the minimum number of stimuli needed for efficient, non-redundant characterization. I term this the One-Stimulus-Per-Factor Principle: one well-chosen stimulus per factor is both necessary and sufficient. A complementary rule governs discovery: at least two to three stimuli per expected factor are needed to establish the factor structure. Converging evidence from luminance and chromatic contrast sensitivity, stereoscopic disparity, motion, hue scaling, face recognition, perceptual organization, and other domains shows that the dimensionality of individual variation is often lower than dense sampling suggests—and sometimes higher than sparse clinical testing captures. The approach also tests construct validity, revealing whether behavioral measures index the mechanisms investigators assume. These findings carry implications for clinical instruments across contrast sensitivity, color vision, stereopsis, and visual field assessment, many of which either oversample a single factor or undersample the full factor space. The same framework clarifies psychiatric applications—including contrast-sensitivity changes in depression, schizophrenia, and ADHD—by separating retinal-neural deficits from optical contributions such as higher-order aberrations and from attentional lapses, and it extends to oculomotor biomarkers. The article develops the Principle as a step-by-step tutorial, with a worked example.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
It is proved that any global minimizer of the trajectory balance objective can define a policy that samples exactly from the target distribution, and empirically demonstrate the benefits of the trajectories balance objective for GFlowNet convergence, diversity of generated samples, and robustness to long action sequenc...
Esmeralda S. Whitammer, Moksh Jain, Emmanuel Bengio et al.· Neural Information Processin...· 302 citations· ⚡60
A machine-learning approach called CheMeleon provides a practical way to develop new drugs or other molecules with much less detailed, expensive experimentation.