Skip to content
#software testing Open access

swmmgi: a reproducible tool and diagnostic protocol for watershed-scale SWMM green-infrastructure modelling

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

Abstract

Open-source, unit-tested Python tool for building watershed-scale EPA SWMM 5.2 green-infrastructure (GI/LID) models from public and incomplete municipal data, with a Gaussian-process-emulator global (Sobol') sensitivity analysis and a transferable forcing/parameter calibration-diagnostic protocol. Companion code for the manuscript prepared for Environmental Modelling & Software. Contributions: Config-driven pipeline handling incomplete municipal storm-sewer data (orphan-outfall reconnection, DEM-Strahler channel augmentation) and SWMM's easily-missed multi-LID stacking constraint. A forcing/parameter calibration-diagnostic protocol (forcing-swap + GP-Sobol' + roughness sweep) localizing model error to forcing, losses, or conveyance, validated on a synthetic twin with known truth (5/5 correct, including the no-error control) and with quantified detection floors. An explicit mass-conservation precondition check. A node-flooding sink, which arises from SWMM's default configuration, can mask a real loss error: holding one loss error fixed while enlarging the sink, a genuine 27% volume error reports as +0.3% at a 21% sink so the protocol returns 'none, within tolerance', and beyond about 60% the sign inverts. Routing continuity error stays at 0.00% throughout and never registers it. Reproducible via tools/twin_masking.py. GP-emulator global sensitivity analysis: channel Manning's n dominates outlet peak Q (total-order index 0.94-0.98 among four sampled parameters). A controlled twin experiment varying only the channel size shows the ranking order is invariant from a free-draining network to 88% flooding loss, while the shares are not: surcharge drives the loss parameter's total-order index from 0.17 to 0.00. A paired 100-member ensemble on the repaired configuration then tests the same question on the real basin. Removing the mass sink leaves the outlet ranking almost unchanged (total-order index for channel n 0.978 to 0.968), so roughness leads there because the reach routes the flood wave rather than because surcharge suppressed the alternatives; at the headwater the loss parameter's share does rise, 0.652 to 0.872. Controlled two-basin build-and-diagnose demonstration (Leon Creek + Lower Medina, San Antonio, TX) plus third-basin generalization: the FOSS (WhiteboxTools/pysheds) pipeline reproduces the reference arcpy channel network within ~1% on length and drainage density (89% spatial overlap) and builds an independent third basin (Headwaters Salado Creek) with no code changes, delineating 98.5% of its mapped area. GI scenario performance and its cross-basin transferability are quantified in a separate companion paper. The demonstration model is reported candidly as uncalibrated for absolute prediction. Acting on the protocol's own verdict shows the raw diagnostics understated the error, because the flooding sink was removing most of the excess runoff; the true event-volume deficit is roughly sixfold. Four candidate mechanisms are then excluded by measurement (gauge-to-node drainage area, unrepresented detention, channel transmission loss, closed-depression storage removed by DEM filling). A fifth, Edwards Aquifer recharge-zone infiltration, is confirmed as a contributor and narrows the bias further. A second masked error then surfaces, since the calibration hyetographs were themselves synthetic: under basin-average radar forcing the wettest-antecedent event closes to within 7% of observed volume. The residual orders by antecedent wetness and is attributed to the model's single fixed soil-moisture state, which continuous simulation would track. Results rest on pipeline validation, sensitivity attribution, and diagnostic error attribution rather than absolute discharge.

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

GPT-Lab Nov 3, 2026

Sovereignty Is the Option to Leave

Is your company’s AI sovereign? A practical guide for CIOs on AI vendor lock-in, EU Data Act switching, cloud sovereignty, and testing your exit plan before you need it. The post Sovereignty Is the Option to Leave appeared first on GPT-Lab.

Microsoft Research Blog Oct 30, 2026

From synthetic enterprise data evaluations to real Microsoft Copilot AI confidence

Evaluating Microsoft Copilot at enterprise scale requires test data that captures the full complexity of real organizations, yet real enterprise data contains sensitive information that cannot be used for evaluation under any circumstances. The post From synthetic enterprise data evaluations to real Microsoft Copilot AI confidence appeared first on Microsoft Research.

Microsoft Research Blog Oct 29, 2026

Microsoft Research Focus – Edition #97

Host Sowbhagya Suresh shares some of the latest news and cutting-edge research from across Microsoft—from understanding the challenges facing coding agents to uncovering how people use AI at work and improving extended-range weather forecasting. The post Microsoft Research Focus – Edition #97 appeared first on Microsoft Research.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.