Data, Code, and Model Artifacts for "Event-based Rainfall–Runoff Modeling with Hydrology-Aware Temporal Convolutional Networks: A Single-Basin Case Study"
Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
This record contains the data, code, trained model artifacts, and evaluation outputs supporting the manuscript “Event-based Rainfall–Runoff Modeling with Hydrology-Aware Temporal Convolutional Networks: A Single-Basin Case Study.” The study evaluates an event-based hydrology-aware Temporal Convolutional Network (TCN) using 144 manually delineated rainfall–runoff events from the NF Newaukum River Above Bear Creek near Forest, Washington (USGS station 12024400) at 15-min temporal resolution. The archived materials include the processed event dataset, fixed temporal train–validation–test partitions, model training and evaluation code, trained weights for the five predefined ensemble members, event-level performance metrics, and outputs from the ablation experiments. The temporal partition comprises 111 training events occurring through 2018, 15 validation events from 2019–2020, and 18 independent test events from 2021–2022. The five ensemble realizations use predefined random seeds 1337, 2026, 42, 777, and 999. The underlying hydrometeorological observations are publicly available from the U.S. Geological Survey for station 12024400. A README file included in this archive describes the directory structure, software requirements, model execution, evaluation workflow, and relationship between the archived files and the results reported in the manuscript. The underlying hydrometeorological observations were obtained from the U.S. Geological Survey National Water Information System for station 12024400 and are public-domain U.S. Government data; the archived processed event files were derived from those observations.
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.