Skip to content
#software testing Open access

Detectability and coverage under restricted access: linear-Gaussian pilots of the blind set

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research)
Meteorological Phenomena and Simulations

Abstract

This record contains the technical note and complete reproducibility package for two linear-Gaussian pilot studies of the “blind set” in physical-state inference. The blind set is defined here as errors that are simultaneously not exposed by the inference system’s available ground-truth-free diagnostics and not covered by its own reported uncertainty in a decision-relevant quantity. The pilots examine the conjecture that such confident, invisible error arises through the interaction of physical access and prior support. Pilot 1 tests whether detectability can be predicted from the model and observation operators alone. Predicted detectability ranked 52 misspecification directions in agreement with realised detection (Spearman ρ = 0.91); the least detectable directions were nevertheless largely covered by the system’s reported uncertainty. Pilot 2 varies access and model-side prior support separately. Errors beyond sensor reach escaped the diagnostics, while the strongest loss of coverage occurred for errors receiving little or no prior support. The results suggest that prior support, rather than binary representability, is the operative model-side factor. The studies are deliberately limited to linear-Gaussian inference on a two-dimensional synthetic degradation field. They are offered as reproducible preliminary evidence and a controlled test of the proposed object, not as evidence that the same behaviour holds for learned, non-linear inference. The accompanying reproducibility package contains all scripts underlying the reported results and Figure 1, fixed random seeds, pinned software versions, raw computational results, a single run_all.py reproduction script, a README mapping each reported result to its generating script, and results/summary.md comparing the reported and reproduced values.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

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. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

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. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

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. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.