Skip to content
#software testing Dataset Open access

Robustness of regulatory colocalization evidence at major depression risk loci — corrective release v2

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

Abstract

CORRECTION OF VERSION 1 This is a corrective release, not an extension of the original findings. The earlier colocalization results are superseded because inappropriate variant-count normalization in posterior combination and cross-gene QTL record selection affected the analyses. The former 130-locus “shared mechanism” category was an operational classification, not evidence of established shared biological mechanisms. Earlier numerical summaries, including 130, 56, and 50.0%, and their affected downstream interpretations must not be reused as validated findings. Corrected gene-specific analysis yields 10,966 gene–locus–tissue tests, 105 default-positive tests involving 88 genes at 55 loci, four tests at three loci stable under all six prior configurations, and cross-resource concordance of 34/81 matched primary-positive tests. These denominators refer to tests rather than independent loci. This release accompanies “Robustness of regulatory colocalization evidence at major depression risk loci.” It contains corrected analysis results, source code, figures, manuscript and supplemental materials, provenance records, numerical validation, and aligned inputs for 417 multi-signal candidates. Version 1 is retained for transparency and the audit trail. The results support a restricted set of regulatory associations. They do not establish tissue-shared mechanisms, verified independent replication, disease specificity, or therapeutic efficacy. Secondary GTEx v10 and immune analyses cover selected subsets. Exact person-level overlap between source studies is not quantified. Missing evidence and non-assessable multi-signal results are not treated as negative findings. Project-authored text and derived results are distributed under CC BY 4.0. Software retains the historical MIT license. Third-party materials remain subject to their providers’ terms; see the included LICENSE and provenance documentation. This work was supported by the General Project of the Zhejiang Provincial Department of Education, China (grant Y202559996), and the Basic Scientific Research Project of the Wenzhou Science and Technology Bureau, China (grant YC20250576). The authors declare no competing interests. Correspondence: Cheng Zhu, School of Mental Health, Wenzhou Medical University, Wenzhou, China.Email: wmuzc@wmu.edu.cnAlternative email: zhucheng871005@163.comORCID: https://orcid.org/0009-0009-2146-5759 All versions: https://doi.org/10.5281/zenodo.22858380Historical version 1: https://doi.org/10.5281/zenodo.22858381

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.