Prespecified analysis plan — voxel-level recovery of the oxygen-transfer constant from exported DSC-MRI capillary-function maps, and its calibration anchor
Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Glioma Diagnosis and TreatmentAdvanced MRI Techniques and Applications
Abstract
Prespecified analysis plan (version 2.0, 21 September 2026) for a methods study of maps exported by a commercial DSC-MRI capillary-function software package. The study tests whether the exported model-based maximum oxygen extraction fraction (OEFmax) map is reproduced voxel by voxel by a published closed-form limiting case of the Jespersen–Østergaard capillary oxygen-extraction model with a single oxygen-transfer rate constant; recovers that constant from the exported maps alone; bounds the reconstruction residual; and identifies the transit-time state at which the constant returns the published calibration target. Secondary analyses address export-side interpolation and the directional curvature of the model along adjacent voxel pairs. Data: 122 patients with untreated IDH-wildtype glioblastoma, the paired-analysable set of a companion study whose feature data are public (doi:10.5281/zenodo.21908596). Native vendor-export grid. No clinical outcome data are used. Status at deposit: deposited before the extraction of voxel-level data. Exploratory analyses carried out earlier on compartment medians are listed with their dates in section 2 of the plan. Files:- Analysis_plan_k_recovery_v2_0_2026-09-21.md — the analysis plan- k_recovery_voxel.py — analysis script, SHA-256 1fcb5c54cbe599e16c0731c5869b18534502ef00ac91c78c294710cc9b8bad71- extract_voxels_export_grid.py — extraction script, SHA-256 edb3949e65653d385192c302b2915894b5e9ba55b421891ef2f15bf1710a18ce Later changes will be recorded as dated amendments in new versions of this record. Results will be deposited in a separate, linked record. Files are restricted until publication of the associated article. The software manufacturer has no role in the design, conduct, analysis or reporting of this study.
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.