4 → 3
Gu Juba activations 1999–2023, old → new
4 → 4
Gu Shabelle activations 1999–2023, old → new
1-in-3.2 → 1-in-3.7
all four windows together, old → new
2–10 days
later on the new model, wherever both models meet the rule (record or forecast)
1What changes
- Activation years. Gu Juba: 2013, 2016, 2018, 2020 on the old model, 2016, 2018, 2020 on the new.
Gu Shabelle: 2013, 2016, 2018, 2020 on the old, 2016, 2018, 2020, 2023 on the new. Both windows drop 2013, which the river
gauges did not record as a Gu flood season on either river; the Shabelle adds 2023, a severe Gu season on the gauges.
- Timing. Wherever both models meet the rule in the same year, on the record or on the forecasts, the new model
meets it later: by 2 to 10 days. The detail per year is in the timing tables below.
- All four windows together (Deyr unchanged on GloFAS version 5, as designed): 8 activations
(1-in-3.2) on the old model, 7 (1-in-3.7) on the new;
severe years caught 7 and 7 of 7;
activations outside a flood season: 2013 and none.
- Levels. The new model runs higher at these points, so the levels rise: Juba points 1.7–2.1
times the old levels, Shabelle points 1.2–1.3 times. Its March–May flows track the SWALIM
gauges about as well as the old model on the Juba (median correlation 0.86 → 0.88) and better on the
Shabelle (0.79 → 0.89).
- Same years throughout. Every old-versus-new comparison on this page uses only the years both versions
cover: the record 1999–2023 (the calibration years) and, for forecasts, the Gu seasons 2016–2023. The new model's
2024 and 2025 are reported separately in section 6.
- Model choice. This page keeps the adopted choice of model per window. A
variant page re-runs that choice with the new Google model as a candidate.
Before Google switches Flood Hub to the new model. On 4 November 2026 the Flood Hub API still
serves the old model (same gauge identifiers, unchanged warning levels). The monitoring pipeline reads Google with Gu levels fitted
on the old model, frozen in the pipeline's threshold file. If the API moves to the new model before those levels are refitted,
the old levels would sit far below the new model's ordinary Gu flows: on the new record they would have activated Gu Juba in
12 and Gu Shabelle in 5 of the 25 Gu seasons 1999–2023. The refitted levels
are the "new level" columns below. Signals that the switch has happened: Flood Hub's warning levels or gauge model identifiers change
for these gauges, or the gauge identifiers move from hybas_ to subhybas_ as in the new dataset (not confirmed).
2The two versions
| Old model (design) | New model (November 2026) |
| Record (reanalysis) | 1980 – Dec 2023 | Dec 1980 – Dec 2025 |
| Forecast archive (reforecast) | issued Jan 2016 – Jun 2023, leads 0–7 days | issued Jan 2016 – Dec 2025, leads 0–10 days |
| Model | lumped, one model per basin | semi-distributed, routed along the HydroBASINS river network |
| Points | the same seven HydroBASINS basins, with identical outlet coordinates (Dollow on the Juba main stem, as live) |
Both versions label days the same way (the record for day T equals the forecast issued on day T+1 at lead 0), so the trigger
page's reading of forecast dates applies to both unchanged. Leads 8–10 of the new forecast archive are not used here,
to keep the action leg as designed.
3Gu Juba: 3 of 4 points over their 1-in-5 level
Each row of the grid is one series, each column one year. River gauges: F a flood season (two gauges over
their own 1-in-3 level), S a severe one (two over 1-in-5). Model rows give the most points over their own
level on any one day of March to May; a filled cell is a year the rule is met (at least 3). Forecast rows mark
a year in which one forecast, at leads of 1 to 7 days, met the rule. Years 1999–2023, the years both versions cover;
forecasts 2016–2023, the Gu seasons both forecast archives cover (hatched before). Hover a cell for details.
| 99 | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 |
|---|
| River gauges | | | | | | | F | | | | | F | | | | | | F | | S | | S | | | S |
|---|
| Old model: points over | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 | 0 | 0 | 4 | 0 | 0 | 4 | 0 | 4 | 0 | 4 | 0 | 0 | 0 |
|---|
| New model: points over | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 0 | 0 | 4 | 0 | 4 | 0 | 4 | 0 | 0 | 2 |
|---|
| Old model: forecast | | | | | | | | | | | | | | | | | | ● | | ● | | ● | | | |
|---|
| New model: forecast | | | | | | | | | | | | | | | | | | ● | | ● | | ● | | | |
|---|
| Old model | New model |
| Activations 1999–2023 | 4 (1-in-6.5) | 3 (1-in-8.7) |
| Severe Gu seasons caught | 2 of 3 | 2 of 3 |
| Severe Gu seasons missed | 2023 | 2023 |
| Activations outside a Gu flood season | 2013 | none |
| Median correlation with the SWALIM gauges, March–May | 0.86 | 0.88 |
When the rule is met
First day the model's own record meets the rule, and first forecast issue date that meets it (leads 1–7 days, read
as on the trigger page: valid day = issue day + lead). The last two columns are the reference from the river gauges: the
day the second gauge crossed its own 1-in-3 level, and how the gauges classed the season.
| Year | Record: old | Record: new | Change |
Forecast: old | Forecast: new | Change | Gauges over 1-in-3 | Gauge season |
| 2013 | 12 Apr | – | – | – | – | – | – | no flood |
| 2016 | 7 May | 14 May | 7 days later | 1 May | 8 May | 7 days later | 1 May | flood |
| 2018 | 21 Apr | 24 Apr | 3 days later | 15 Apr | 18 Apr | 3 days later | 17 Apr | severe |
| 2020 | 30 Apr | 4 May | 4 days later | 24 Apr | 28 Apr | 4 days later | 22 Apr | severe |
Old model
New model
the rule's level (100%)
Daily flow at the point ranked 3rd highest of 4, as a share of
that point's own 1-in-5 level, March to May, on each model's record. The rule is met on days the line reaches
100%; dots mark the first such day. Years shown: every year from 1999 to 2023 in which either model or either forecast met the rule.
Levels at each point
1-in-5 level fitted on the March–May seasonal maxima 1999–2023 of each model's own record (Weibull
plotting position, as in the trigger analysis) and mean March–May flow (m³/s), and the best-lag rank correlation with the
point's SWALIM gauge, computed as in the trigger page's station table.
| Point | Old level | New level | New / old |
Old mean | New mean | Old correlation | New correlation |
|---|
| Dollow | 508 | 845 | 1.66x | 166 | 237 | 0.86 | 0.88 |
| Luuq | 433 | 833 | 1.92x | 126 | 231 | 0.87 | 0.89 |
| Bardheere | 377 | 809 | 2.14x | 105 | 219 | 0.86 | 0.88 |
| Bualle | 391 | 796 | 2.04x | 105 | 208 | 0.88 | 0.87 |
Other return periods, same vote count
| Level | Old model, years | New model, years |
| 1-in-3 | 2003, 2010, 2013, 2016, 2018, 2020, 2023 | 2005, 2010, 2013, 2016, 2018, 2020, 2023 |
| 1-in-4 | 2010, 2013, 2016, 2018, 2020 | 2010, 2013, 2016, 2018, 2020, 2023 |
| 1-in-5 | 2013, 2016, 2018, 2020 | 2016, 2018, 2020 |
| 1-in-6 | 2013, 2016, 2018, 2020 | 2016, 2018, 2020 |
4Gu Shabelle: 2 of 3 points over their 1-in-6 level
Each row of the grid is one series, each column one year. River gauges: F a flood season (two gauges over
their own 1-in-3 level), S a severe one (two over 1-in-5). Model rows give the most points over their own
level on any one day of March to May; a filled cell is a year the rule is met (at least 2). Forecast rows mark
a year in which one forecast, at leads of 1 to 7 days, met the rule. Years 1999–2023, the years both versions cover;
forecasts 2016–2023, the Gu seasons both forecast archives cover (hatched before). Hover a cell for details.
| 99 | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 |
|---|
| River gauges | | | | | F | | F | | | | | F | | | | | | S | | F | | S | | | S |
|---|
| Old model: points over | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 | 0 | 0 | 3 | 0 | 3 | 0 | 3 | 0 | 0 | 0 |
|---|
| New model: points over | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 | 0 | 3 | 0 | 3 | 0 | 0 | 3 |
|---|
| Old model: forecast | | | | | | | | | | | | | | | | | | ● | | ● | | ● | | | ● |
|---|
| New model: forecast | | | | | | | | | | | | | | | | | | ● | | ● | | ● | | | ● |
|---|
| Old model | New model |
| Activations 1999–2023 | 4 (1-in-6.5) | 4 (1-in-6.5) |
| Severe Gu seasons caught | 2 of 3 | 3 of 3 |
| Severe Gu seasons missed | 2023 | none |
| Activations outside a Gu flood season | 2013 | none |
| Median correlation with the SWALIM gauges, March–May | 0.79 | 0.89 |
When the rule is met
First day the model's own record meets the rule, and first forecast issue date that meets it (leads 1–7 days, read
as on the trigger page: valid day = issue day + lead). The last two columns are the reference from the river gauges: the
day the second gauge crossed its own 1-in-3 level, and how the gauges classed the season.
| Year | Record: old | Record: new | Change |
Forecast: old | Forecast: new | Change | Gauges over 1-in-3 | Gauge season |
| 2013 | 6 May | – | – | – | – | – | – | no flood |
| 2016 | 12 May | 15 May | 3 days later | 30 Apr | 9 May | 9 days later | 11 May | severe |
| 2018 | 5 May | 7 May | 2 days later | 27 Apr | 1 May | 4 days later | 7 May | flood |
| 2020 | 30 Apr | 9 May | 9 days later | 22 Apr | 2 May | 10 days later | 5 May | severe |
| 2023 | – | 9 May | – | 26 Apr | 3 May | 7 days later | 17 Apr | severe |
Old model
New model
the rule's level (100%)
Daily flow at the point ranked 2nd highest of 3, as a share of
that point's own 1-in-6 level, March to May, on each model's record. The rule is met on days the line reaches
100%; dots mark the first such day. Years shown: every year from 1999 to 2023 in which either model or either forecast met the rule.
Levels at each point
1-in-6 level fitted on the March–May seasonal maxima 1999–2023 of each model's own record (Weibull
plotting position, as in the trigger analysis) and mean March–May flow (m³/s), and the best-lag rank correlation with the
point's SWALIM gauge, computed as in the trigger page's station table.
| Point | Old level | New level | New / old |
Old mean | New mean | Old correlation | New correlation |
|---|
| Belet Weyne | 346 | 434 | 1.25x | 95 | 99 | 0.81 | 0.89 |
| Bulo Burti | 362 | 431 | 1.19x | 94 | 98 | 0.79 | 0.90 |
| Jowhar | 361 | 428 | 1.18x | 94 | 95 | 0.78 | 0.84 |
Other return periods, same vote count
| Level | Old model, years | New model, years |
| 1-in-3 | 2000, 2005, 2010, 2013, 2016, 2018, 2020, 2023 | 2005, 2010, 2013, 2016, 2018, 2020, 2021, 2023 |
| 1-in-4 | 2005, 2010, 2013, 2016, 2018, 2020 | 2005, 2010, 2016, 2018, 2020, 2023 |
| 1-in-5 | 2005, 2013, 2016, 2018, 2020 | 2010, 2016, 2018, 2020, 2023 |
| 1-in-6 | 2013, 2016, 2018, 2020 | 2016, 2018, 2020, 2023 |
5All four windows together
The allocation is sized on the union of the four windows. Deyr runs on GloFAS version 5 as designed and is the same in both
rows (2006, 2023 on the Juba, 2006, 2014, 2019, 2023 on the Shabelle). Severe years are
those in which two gauges on a river crossed their own 1-in-5 level in either season (2006, 2014, 2016, 2018, 2019, 2020, 2023).
| Gu windows on | Activations | Return period | Years | Severe caught | Severe missed | Outside a flood season |
| Old model | 8 | 1-in-3.2 | 2006, 2013, 2014, 2016, 2018, 2019, 2020, 2023 | 7 of 7 | none | 2013 |
| New model | 7 | 1-in-3.7 | 2006, 2014, 2016, 2018, 2019, 2020, 2023 | 7 of 7 | none | none |
The windows were calibrated jointly to about 1-in-3 on the old model. On the new model the same settings activate less often
(1-in-3.7). Whether to re-tune for the new model is a design decision for the working group; this page only
shows the adopted settings carried over.
6New model only: 2024 and 2025
The new record and forecast archive run two years past the old ones, so these years have no old-model counterpart and are
kept out of every comparison above. Levels are still those fitted on 1999–2023; the gauge season uses the same gauge levels
on the gauges still reporting.
| Window | Year | Most points over on one day | Record |
Forecast (leads 1–7) | Gauge season |
|---|
| Gu Juba | 2024 | 4 of 4 | met, 10 May | met, issued 5 May | flood |
| Gu Juba | 2025 | 0 of 4 | not met | not met | not assessable |
| Gu Shabelle | 2024 | 0 of 3 | not met | not met | severe |
| Gu Shabelle | 2025 | 0 of 3 | not met | not met | no flood |
7Method
- Exactly the trigger page's code (
scripts/page_additions/somlib.py), run on each model's data in turn:
per-point levels by Weibull plotting position with log-log interpolation on March–May maxima 1999–2023; a day
counts when at least the required number of points are at or over their own level; forecasts at leads 1–7 days
against the same levels.
- Same years for both versions: levels fitted on 1999–2023 for both; activations, timing, scores, correlations and the
old-levels-on-new-flows count all over 1999–2023; forecasts over the Gu seasons 2016–2023.
- The river-gauge benchmark is unchanged (two SWALIM gauges over their own level, levels fitted 2000–2023).
- The old model run here reproduces the adopted Gu activation years (2013, 2016, 2018, 2020 on both rivers).
- Data: Google Runoff Reanalysis & Reforecast, public Google Cloud bucket
flood-forecasting,
old version model_id_8583a5c2_v0, new version distributed_model_2026_11 (CC-BY-4.0).