H1
How small can it get?
Measure how multi-step accuracy falls as the model shrinks to browser size, as a curve of size against rollout horizon.
Understand · Stage 7
There are no model results yet. This page records what the project is trying to find out, so the claims can be checked against the outcome later.
H1
Measure how multi-step accuracy falls as the model shrinks to browser size, as a curve of size against rollout horizon.
H2
Larger flood models can already warn when they leave their training range, but the usual method multiplies download size. Test which cheap signal best predicts rollout failure on edited scenarios.
H3
Train only on simulated floods, start from the observed 30 November state, and score on the observed 3 December state, only where both images saw the ground. It must beat a no-change baseline. Little rain fell between the two images, so this mainly tests draining. One case study, not proof.
H4
Train the same model with no weather, with rainfall, and with rainfall and cloud, then measure what each input adds per kilobyte. Not yet checked against the literature.
Status: narrowed by a first literature screen in November 2026. It was a short search, not a systematic review, so "not found" does not prove a gap. Any question found to be answered elsewhere will be replaced.
From the first screen. Not every paper here has been read in full yet.
Water-level forecasting at Hanwella with models including XGBoost. Not a spatial world model.
Very close to the architecture considered here, so it is a baseline to beat or borrow from.
Interactive analysis of observed impacts. No learned dynamics.
Shows learned models struggle in unfamiliar conditions, which motivates H2.
A long rollout tested on real events, using one 2.7 million parameter model on a GPU. It starts from spin-up, not a mapped flood.
Ensembles already warn when a flood surrogate leaves its training range, so H2 must be about affordable warnings.
A surrogate of about 0.7 MB in the browser, for steady airflow. It has no time-stepping, and clamps sliders to its training range.
The same storm also caused landslides. UNESCO maps about 2,163 ha of them. That layer is downloaded and measured, and the design keeps terrain and weather inputs separate from each hazard. No landslide model exists. It needs its own study area and its own mathematics, as the guide explains.
Repository, static deployment and portfolio link.
Real UNESCO and Copernicus flood layers on an aligned map.
Half-hourly IMERG rainfall and Copernicus terrain added to the explorer.
A simplified 32 by 32 water-flow simulator, not validated hydrology, and synthetic training data.
Small PyTorch models trained with and without weather, adding cloud and inflow data.
The trained model exported to ONNX and run on the visitor's device.
Validation against the real event, limitations and the article.
A separate landslide head that reuses the terrain and weather inputs.