SFINCS

Run the pipeline stages in order: setup_sfincs_domain.py to define the grid, build_sfincs_topobathy.py for DEM processing, prepare_sfincs_rainfall.py for forcing, generate_sfincs_inp.py for configuration, then run_sfincs.py to execute. The binary reads sfincs.inp from the current working directory.

Use cama_to_sfincs_boundary.py to convert CaMa-Flood discharge (m3/s) or water level into sfincs.src/.dis or sfincs.bnd/.bzs files. Avoid double-counting precipitation: give SFINCS its own rainfall and use CaMa-Flood only for river boundary inflow.

CaMa-Flood routes water through 15-arcmin (~28km) river networks for global-scale flood extent. SFINCS solves 2D shallow water equations at 10-200m resolution for local flood depth, supporting coastal surge, rainfall, and urban flooding. They are complementary in a cascade workflow.

The most common cause is precipitation units: SFINCS expects mm/hr, but CMFD provides kg/m2/s (multiply by 3600) and VIC forcing is mm per 3-hour timestep (divide by 3). Also check that precipfile (ASCII) is used instead of netprecipfile, which can silently fail.

Mask value 2 is a water-level boundary held at 0.0m, which drains inland terrain above sea level. For inland river reaches use mask=3 (absorbing outflow) on the downstream edge only, via build_sfincs_topobathy.py --outflow_value 3.

Validation requires independent water observations: SAR inundation masks for flood extent (CSI scoring) or stage gauges for water level. A DEM is not a flood observation, and scoring a gauge forced by its own discharge is circular; use a two-station setup with an independence screen.