What can be expected from a semi-distributed multi-model approach for streamflow forecasting? Tailoring the structure and size of a super-ensemble on the Rhône basin
Bibliographic record
Abstract
• Using a super-ensemble improves streamflow forecasting regardless of the lead time. • We developed dynamic and static combination approaches to reduce the size of the super-ensemble. • Reducing super-ensemble complexity with these methods does not impair the forecast. • Semi-distribution brings no benefit compared with the lumped approach on average over our test sample. Streamflow forecasting is useful for various purposes, from ensuring the safety of populations during floods to managing hydraulic structures. The aim of this work is to combine two hydrological modelling approaches widely used in streamflow forecasting in order to define their benefits and limits in a probabilistic framework: the multi-model approach (which accounts for structural and parametric model uncertainty) and the semi-distributed approach (which considers explicitly the spatial variability of precipitation and hydrological processes). The study focuses on 12 tributaries of the Rhône River, which were modelled using 39 hydrological model configurations. Tests were carried out at an hourly time step for lead times ranging from 1 h to 120 h, considering ensemble meteorological forecasts. The results show that explicitly considering uncertainty with a probabilistic super-ensemble (meteorological ensemble chained to a multi-model approach) improves the quality of streamflow forecasts. On the other hand, there is no clear benefit from a semi-distributed approach compared with a lumped framework. This paper also explored the structure and size of the super-ensemble, showing that it is possible to reduce its complexity through model selection or combination methods without impairing predictive performance. This study provides valuable insights into the strengths and limitations of a super-ensemble approach and how to limit its complexity, contributing to the ongoing efforts to improve streamflow forecasting for operational purposes.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.007 | 0.015 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.002 | 0.005 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".