Replication materials for "Spatial autocorrelation of suicide mortality worldwide at three time points spanning the COVID-19 pandemic period: 2019, 2021, and 2023"
Oct 2026· Zenodo (CERN European Organization for Nuclear Research)
Suicide and Self-Harm Studies
Abstract
Replication materials (data and code) for the manuscript "Spatial autocorrelation of suicide mortality worldwide at three time points spanning the COVID-19 pandemic period: 2019, 2021, and 2023", submitted to PLOS Global Public Health (PGPH-D-26-02463). The package contains: (1) the analytical dataset for 203 countries with age-standardized suicide mortality rates (Global Burden of Disease 2023, self-harm cause, both sexes) for 2019, 2021 and 2023, death-registration completeness (International Completeness of Death Registration database, 2015–2019), LISA classifications, local pseudo p-values, Benjamini-Hochberg q-values and descriptive trajectory labels; (2) the GBD 2023 data extracts; (3) a single canonical R script that reproduces every value reported in the manuscript, including global Moran's I and LISA with five-nearest-neighbour weights and 9999 permutations (seed 42), Benjamini-Hochberg false-discovery-rate correction applied separately within each year, the Friedman test, Wilcoxon signed-rank comparisons with Holm correction, Kendall's W, the exact McNemar test, the complete-registration sensitivity analysis and the robustness analyses; (4) the full log of the run from which all reported values are taken; and (5) the Python script used to draw the figures. Software environment: R 4.5.1 with sf 1.0.23, spdep 1.4.1 and rnaturalearth 1.2.0. Country boundaries: Natural Earth 1:50 m (public domain). See README.md for the codebook and reproduction instructions. Version 3: the canonical analysis script now produces every value reported in the manuscript, including the Benjamini-Hochberg FDR correction applied within each year and the exact McNemar test. The full run log and the country-level local pseudo p-values and q-values are included. All files are in English.
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.· arXiv.org· 727 citations· ⚡54
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.· Empirical Software Engineeri...· 401 citations· ⚡48
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.· Information and Software Tec...· 394 citations· ⚡54
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· IET Software· 238 citations· ⚡9
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.· Journal of Systems and Softw...· 236 citations· ⚡13
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.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
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.
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…
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.