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

Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 728 citations · ⚡54
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, 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 Open access Jul 2017

What happens when software developers are (un)happy

The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.

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

Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Aug 17, 2026

Q&A: Rethinking how innovation happens

In his latest book, Professor Eugene Fitzgerald examines the forces that turn breakthroughs into value — and why innovation resists simple formulas.