Lund University

2 related articles

Subscribe to updates

medRxiv Oct 11, 2026
Coronary risk scores stop giving one number: eight biological axes separate people with the same genetic liability
Polygenic risk for coronary artery disease no longer collapses into a single number. Conventional scores identify who is at high risk but not which biological processes drive that risk. Decomposing 526 genome-wide significant variants by their associations with 78 CAD-related traits yielded eight latent components: cholesterol-enriched lipoproteins, triglyceride-rich lipoproteins, lipoprotein(a), metabolically unhealthy normal weight, obesity, endothelial dysfunction, coagulation and cardiac remodeling. Process-specific scores built in UK Biobank, SCAPIS and Mass General Brigham Biobank tracked clinical coronary events, subclinical atherosclerosis and distinct biomarker and comorbidity profiles.
Polygenic risk for coronary artery disease no longer collapses into a single number. Conventional scores identify who is at high risk but not which biological processes drive that risk. Decomposing 526 genome-wide significant variants by their associations with 78 CAD-related traits yielded eight latent components: cholesterol-enriched lipoproteins, triglyceride-rich lipoproteins, lipoprotein(a), metabolically unhealthy normal weight, obesity, endothelial dysfunction, coagulation and cardiac remodeling. Process-specific scores built in UK Biobank, SCAPIS and Mass General Brigham Biobank tracked clinical coronary events, subclinical atherosclerosis and distinct biomarker and comorbidity profiles.
Lund University University of Gothenburg KTH Royal Institute of Technology Harvard University Chalmers University of Technology Uppsala University Sahlgrenska University Hospital Broad Institute
Jakub Morze（First author）Clemens Wittenbecher（Corresponding author）
Coronary Artery Disease Polygenic Risk Score Bayesian Non-negative Matrix Factorization Chromatin Accessibility Enrichment Analysis
arXiv Sep 26, 2026
15-day field study in an industrial C++ repository: after AI mass remediation, CI and review became the main bottlenecks, and directory-based batching with a per-change file cap restored throughput
In a 15-day exploratory single-case field study in a closed-source industrial C++ repository, an experienced developer used a command-line AI coding buddy to remediate widespread issues, triangulating Gerrit metadata with a developer diary and team chat through descriptive statistics and qualitative coding; AI-assisted remediation rapidly generated hundreds of commits touching thousands of lines, saturating build-on-commit CI and reviewer attention, naive per-file commits overloaded CI, and switching to directory-based batching with a cap on files per change restored throughput, yet still required explicit review solicitation, negotiation of acceptable commit granularity, and iterative follow-up to resolve build and static-analysis failures, showing that when mechanical editing becomes che
In a 15-day exploratory single-case field study in a closed-source industrial C++ repository, an experienced developer used a command-line AI coding buddy to remediate widespread issues, triangulating Gerrit metadata with a developer diary and team chat through descriptive statistics and qualitative coding; AI-assisted remediation rapidly generated hundreds of commits touching thousands of lines, saturating build-on-commit CI and reviewer attention, naive per-file commits overloaded CI, and switching to directory-based batching with a cap on files per change restored throughput, yet still required explicit review solicitation, negotiation of acceptable commit granularity, and iterative follow-up to resolve build and static-analysis failures, showing that when mechanical editing becomes che
Lund University Ericsson (Sweden)
Andreas Bexell（First author）
AI-Assisted Code Remediation code review continuous integration bottleneck

You’re all caught up

Coronary risk scores stop giving one number: eight biological axes separate people with the same genetic liability

15-day field study in an industrial C++ repository: after AI mass remediation, CI and review became the main bottlenecks, and directory-based batching with a per-change file cap restored throughput