Skip to content
#software testing Open access

mic-plan benchmark protocol

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research) · 2 citations

Abstract

This record registers, before any power or classification was computed, the protocol and the complete code of a benchmark of the Python package mic-plan 1.0.0 against ten sample-size methods for studies that compare minimum inhibitory concentration (MIC) distributions. The methods are stats::power.prop.test, Hmisc::posamsize (Whitehead 1993), samplesize::n.wilcox.ord (Zhao et al. 2008), WMWssp (Happ et al. 2019), pwr::pwr.chisq.test with Cohen's w, stats::power.t.test on mean log2 MIC (after Zawack et al. 2016), simulation at the pilot proportions, posterior-average power, and the 90th percentile of the Zhao et al. size over pilot bootstrap resamples and over Dirichlet posterior draws. Every plan is judged against the true power of the test it implies. The validation set holds every 2021 EFSA stratum of indicator Escherichia coli with at least 150 isolates and every 2021 FDA NARMS cecal E. coli stratum with at least 150 isolates for ampicillin, chloramphenicol, ciprofloxacin and tetracycline (130 distributions, three changes each, 20 pilots of 20 isolates); no computation of the project had used these distributions. The development sets hold the 2023 distributions used while mic-plan was built and in an earlier six-method comparison (doi:10.5281/zenodo.22997395). Hypotheses: H1, mic-plan leaves at most 10% of its validation plans below 80% power; H2, fewer than each of the eight published methods (Holm adjustment); H3, a positive control for four point-estimate methods. BENCHMARK_PROTOCOL.json gives the laws, changes, methods, analysis tests, truth calculation, endpoints, hypotheses and decision rules (protocol digest 35a3e62ace71ab8ca0bc327b32a27fcb781324880998f5c2f4dc75af071436e9). SIZE_CHECK.json shows that the six formula-based sizes agree with the R packages on all 23,580 pilots; before this deposit only sizes had been computed, apart from a software check that also estimated three power points of one validation law (law 519 at 160 isolates per group for the rank, chi-square and t-tests); these were not classified or used.

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.