Skip to content
#software testing Open access

Reproducibility artifact for "The compression defect of a discrete-sine Galerkin section" (Part I) and "The exact row of the Toeplitz–Cayley model" (Part II)

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

Abstract

Version 1.3 accompanies version 1.1 of Part II of the series, "The exact row of the Toeplitz–Cayley model: coefficient law, Binet–Laguerre remainder, and certified positivity at finite rank" (https://doi.org/10.5281/zenodo.22285620; concept DOI https://doi.org/10.5281/zenodo.22276540). New in this version: the research checkpoint frontier_v0_57 — the post-publication audit of Part II version 1.0 (blind re-derivation of the theorems by scripts that import no code of the project, every prose number recomputed, and two adversarial blocks: an independent end-to-end reproduction of a certified eigenvalue of Table 4 by a Cauchy-integral route, and the envelope, the budget and the transfer tested on that independent row at N = 625), the certified saturation check of the enveloping theorem in Arb ball arithmetic (N = 300, 625, 5000; K = 1..7: supremum of the ratio, attainment at d = 1, sign, two-sided row sums; the source of every number of the new Remark 3.7), the verbatim reports of six adversarial reviews (two of the revision, two complete re-readings of the notes, two verification passes) and the finding-by-finding review record, the q = 11/4 certificate of Part I replayed at N = 1250, 2500, 5000, and the deposited PDF and LaTeX sources of Part II version 1.1 (https://doi.org/10.5281/zenodo.22285620) and Part I version 1.3 (https://doi.org/10.5281/zenodo.22286746). The earlier versions of the notes, shipped in versions 1.0–1.2 of this archive inside the sealed checkpoints, are not shipped in version 1.3 because their title footnote carried a personal address (PACKAGE_REDACTIONS.md lists them with their hashes); no script, data file or replay report is affected. Replay: sh recovered_work/frontier_v0_57/REPRODUCE.sh /path/to/python [--n5000] (283 s, plus about 5 min with --n5000), or sh REPRODUCE.sh /path/to/python --audit from the top level. The cached exact rows are unchanged: the seven row archives of this record are those of version 1.2. Companion research software and audit archive for the two notes. It contains the scripts, the pinned historical inputs, the pre-computed replay reports, SHA-256 manifests of every file, and the notes themselves with their LaTeX sources. Every table entry, figure and certified enclosure displayed in Part II is produced by a script of this package, and every prose number is traceable to one of its replay reports. Requirements: Python 3.10 or later for Part I and 3.11 or later for Part II (the versions the replays were run on), python-flint 0.9.0 (Arb ball arithmetic), mpmath, numpy 2.x, matplotlib. Full replay of Part I: sh REPRODUCE.sh /path/to/python (a few minutes); of Part II: sh recovered_work/frontier_v0_54/REPRODUCE.sh and sh recovered_work/frontier_v0_55/REPRODUCE.sh (about three hours each on one core). Statements of a definite sign are decided only in ball arithmetic, on the appropriate one-sided endpoint; float64 scripts are labelled as probes and decide nothing. Reference environment: Linux x86-64, Python 3.11, python-flint 0.9.0, mpmath, NumPy 2.4.4, matplotlib; Part I additionally replayed on macOS 15 arm64 (Python 3.14.6) and on Linux x86-64 (Python 3.10.12). The artifact is distinct from the notes and has no direct implication for the Riemann hypothesis. Original code is MIT-licensed; project-authored documentation is CC BY 4.0, as detailed in the licence files inside the archive. Anthropic Claude assisted with preparation; Julien Lange is the sole author and assumes responsibility for the release. Versions 1.0, 1.1 and 1.2 of this archive, which contained those earlier versions of the notes, are withdrawn from the repository by the author on the day of this deposit.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 728 citations · ⚡54
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, 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 Open access Jul 2017

What happens when software developers are (un)happy

The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.

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

Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.

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

Related blog posts

MIT News · Artificial Intelligence Aug 17, 2026

Q&A: Rethinking how innovation happens

In his latest book, Professor Eugene Fitzgerald examines the forces that turn breakthroughs into value — and why innovation resists simple formulas.