Skip to content
#software testing Open access

CPU-only maximum verification suite for qector-decoder-v3 1.0.0 under an Enterprise license.

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

Abstract

CPU-only maximum verification suite for qector-decoder-v3 1.0.0 under an Enterprise license. This deposit contains the complete pytest suite, machine report, and supporting artifacts used to confirm syndrome-faithful batch decoding on CPU across eleven code families and twenty-two decoder backends. Distances from 3 to the Enterprise cap of 63 were exercised. All 376 tests passed with zero failures. Key results- 100 % syndrome faithfulness (H c = s mod 2) on every checked shot- Code families: repetition, ring, rotated surface, unrotated surface, toric, heavy-hex, colour code, hypergraph product, bicycle, bivariate bicycle, and arbitrary parity-check matrices- Decoder backends include Union-Find, Fast Union-Find, Blossom, Sparse Blossom, BP-OSD, Hybrid Cascade, AutoDecoder, Space-Time, Streaming, Sliding-Window, and related variants- Shot ladder from 1 to 1 000 000; extreme-shot and robustness cases included- Enterprise distance cap verified: d = 63 accepted, d = 64 correctly rejected with PermissionError- Host: AMD EPYC 7V12 (4 cores / 8 logical), 28 GiB RAM, Windows 11, Python 3.11, pure CPU (no CUDA / OpenCL) Contents- Full pytest suite (test_00 to test_11 plus conftest and harness)- CPU_MAX_REPORT.json (structured machine and result metadata)- QECTOR_CPU_MAX_ZENODO_PRO_REPORT.pdf and its SHA-256 checksum- zenodo_deposit_metadata.json Reproducibility noteAn active Enterprise license key is required to execute the full suite and to reach distance 63. Community and Pro tiers are limited to lower distances by design. Throughput numbers are host-specific and are reported only as measured on the listed hardware; they are not claimed as portable performance guarantees. Related records- Reference Manual v1.0.0: 10.5281/zenodo.21941046- Companion publication: 10.5281/zenodo.22244510 Software: qector-decoder-v3==1.0.0Generated: 2026-09-04 Licensing clarification The pytest suite, report and deposited artifacts in this record are shared under CC-BY-4.0 for verification materials (see Licensing below). The software under test (qector-decoder-v3 1.0.0, installed from PyPI) is distributed under an Enterprise license key regime: an active Enterprise key is required to execute the full suite and to reach distance 63 (Community and Pro tiers are limited to lower distances by design). The CC-BY-4.0 license on this record covers the deposited verification materials only, not the commercial licensing terms of the software itself. Licensing This record contains two categories of material, licensed under different terms. Data, reports, and documentation (datasets, JSON and CSV artifacts, figures, PDF reports, certificates, Markdown and text reports): made available under the Creative Commons Attribution 4.0 International License (CC-BY-4.0). You may share and adapt this material, including for commercial purposes, provided you give appropriate credit to Guillaume Lessard / iD01t Productions and indicate if changes were made. Code (all .py files, .pyi stubs, notebooks, and scripts): licensed under the PolyForm Noncommercial License 1.0.0. You may use, copy, and modify the code for noncommercial purposes only. Any commercial use, including use in or to develop a commercial product or service, requires a separate commercial license from iD01t Productions. The full license text is included in this record (LICENSE-POLYFORM-NONCOMMERCIAL-1.0.0) and at https://polyformproject.org/licenses/noncommercial/1.0.0/ . Copyright (c) 2026 Guillaume Lessard / iD01t Productions. All rights reserved except as expressly granted above. Note on prior versions: earlier versions of this record were published with a CC-BY-4.0 metadata license. That grant is irrevocable for copies already obtained under it. The terms above apply to this version and all future versions.

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.