These are “how the pieces usually fit together” references. Each repository contains the authoritative, detailed instructions.
Hydrology & Forecasting workflow
Typical operational chain around Hydrological Model Continuum (HMC) and the Flood‑PROOFS stack.
- Collect & prepare inputs (observations, NWP, static layers) — often via HyDE-like data engines.
- Run the hydrological core (HMC) using wrappers such as
fp-hmc.
- Optional cryospheric coupling: run S3M (snow/glacier) and feed outputs into hydrologic modelling.
- Post-process: quality control, aggregation, indicators, verification.
- Publish & visualize: dashboards, maps, reports, or downstream services.
Drought analysis workflow
Typical pipeline for drought monitoring with DRYES and companions.
- Acquire time series / rasters from meteorological, satellite, or model products (often via DOOR).
- Standardize datasets and compute intermediate layers with DAM (middleware utilities).
- Compute drought indicators (indices, anomalies, persistence metrics) with DRYES.
- Summarize & report by administrative units / basins; create maps and time series.
Near real-time flood hazard mapping
Example workflow where model outputs are turned into hazard maps.
- Hydro‑meteorological forecasts feed the operational chain.
- Hydrologic simulation produces discharge/runoff estimates.
- Flomart generates flood hazard maps in near real time for dissemination and decision support.
Reproducibility checklist
Good practice for operational and research workflows.
- Pin versions (tags/releases), capture run settings and input data provenance.
- Use configuration files, avoid hard-coded paths, document dependencies.
- Add simple smoke tests and example runs (small domains) for CI.
