Skip to content
#software testing Dataset Open access

Data and code for: The feasibility gap of magnitude-threshold traffic-light schemes for induced seismicity in the southern Sichuan Basin: root causes and operational alternatives

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

Abstract

Data and analysis code accompanying the manuscript “The feasibility gap of magnitude-threshold traffic-light schemes for induced seismicity in the southern Sichuan Basin: root causes and operational alternatives” (Qi Deng, submitted to Journal of Seismology). The study asks how much advance warning a conventional magnitude-threshold traffic-light scheme (TLS) could have delivered before the moderate earthquakes of the southern Sichuan Basin between 2015 and 2024, and tests seven published and bounding designs against the full 2010–2024 open record. The deposit contains the earthquake catalogues used, the derived event lists, the development-zone geometry, and the complete Python analysis code, including the traffic-light back-test, the goodness-of-fit and sensitivity analyses, and the figure generator. Contents Mapped fault traces shown in Fig. 1 are extracted from the China Active Faults Database (1:4 000 000; Wu et al. 2024, Earth Syst. Sci. Data 16, 3391–3417, doi:10.5194/essd-16-3391-2024) and shipped in ESM_4.zip. ESM_1.csv (Online Resource 1) – USGS PDE catalogue for the Yibin region, 2010-01-01 to 2024-12-31, M ≥ 3.0 (239 events after removal of non-earthquake records) ESM_2.txt (Online Resource 2) – ISC Bulletin agreement-check counts by year, 2010–2024 ESM_3.csv (Online Resource 3) – complete M ≥ 4.5 event list (117 events) ESM_4.zip (Online Resource 4) – catalogue download, completeness, phase-rate and sensitivity scripts, the mainshock-migration test, and the figure / graphical-abstract generators ESM_5.json (Online Resource 5) – approximate development-zone centres and bounds used for all distance statistics ESM_6.zip (Online Resource 6) – the complete traffic-light back-test (Sections 4.4, 4.5–4.9 of the manuscript), with its own README containing full definitions and run instructions ESM_7.zip (Online Resource 7) – the local-catalogue verification of Section 4.10: the relocated Changning–Gongxian catalogue (Anyiam et al. 2023) and dense-array catalogue (Zhang et al. 2024), the cross-catalogue calibration, completeness estimates, the 10-km-buffer back-test and its scripts, with its own README SUPPLEMENTARY_README.txt – file manifest Traffic-light back-test (ESM_6). S6_tls_backtest.py defines the seven designs, builds the daily traffic-light state series, and performs the back-test and the Gutenberg–Richter extrapolation; S7_tls_figure.py reproduces Fig. 5; S8_spatial_buffer.py carries out the spatial-buffer sensitivity of Section 4.7 — the scheme armed only on events within a radial buffer around each development zone, at R = 5, 10, 15, 20 and 30 km; S9_sensitivity.py runs the magnitude-scale-offset sweep and the 2019-01-03 Gongxian sensitivity; and S10_bvalue_gof.py performs the goodness-of-fit test of the fitted Gutenberg–Richter law (Kolmogorov–Smirnov with a Monte-Carlo, parameter-estimation-corrected p-value whose null distribution is simulated at the catalogue's 0.1 magnitude reporting precision) together with the declustered b-values of Section 4.9. Every script reads only from data/ and writes only to out/; the machine-readable results underlying Fig. 5 and Tables 6–7 are included. Runtime is a few seconds per script and no network access is required. Key results reproduced here. Every published design whose red threshold lies at or below ML 4.0 collapses to a single rule on an M ≥ 4.0 catalogue (red on 62.8% of armed days, 38 stop-work episodes in ten years). Raising the threshold to the highest still enforceable value (M 5.0) removes the saturation but leaves four of the seven armed-period mainshocks without any live escalation. Restricting the scheme to the 10–20 km footprint at which these protocols are enforced lowers saturation to 11.5–20.7% but leaves site-specific capture at 43%, so the failure mode moves from false alarms to missed events rather than disappearing. No red threshold between M 4.0 and M 6.0 achieves both 50% precursor capture and a 30-day exceedance interval. Data sources. The raw catalogues are openly available from the USGS PDE (earthquake.usgs.gov/fdsnws) and the ISC Bulletin (fdsnws.isc.ac.uk); they are redistributed here for reproducibility. The China Earthquake Networks Center catalogue was not accessible under the author's institutional data-access constraints; where Chinese-network magnitudes are quoted they are taken from published values and are listed in Table 3 of the manuscript. Software. Python 3.13 with NumPy, pandas, SciPy and matplotlib. License: CC BY 4.0.

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.