Dam Break Inundation Modelling Using Hydrodynamic Modelling of any River

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   Flood hydrodynamics is genuine CFD, and breach parameterisation, numerical stability and boundary conditions all have to be right or the simulation is confidently wrong

2. It gets worse

   Validation is hard — without observed flood extents you cannot verify your inundation map, and a judge will ask exactly how you know it is correct

3. Still reading?

   SPH for a catchment-scale flood is computationally heavy, so naive implementation will not run at useful resolution in reasonable time

4. And the finisher

   DEM resolution limits inundation accuracy in exactly the narrow valleys where flash floods are most dangerous

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  3/5

  Buildable. Not comfortably. There is a week in here you have not planned for yet.

  Free DEMs and satellite imagery are available and open hydrodynamic solvers exist, but shallow-water and SPH flood modelling is genuine computational fluid dynamics requiring correct physics, breach parameterisation and numerical stability, and validating the result without observed flood data is hard — this is specialist hydraulics rather than an application build.

• Innovation scope

  3/5

  Mildly interesting. The novelty will not carry the room; the build has to.

  The physics is established and the description even names the modelling methods, so your room is in the automation, the terrain preprocessing and the scenario comparison rather than in the modelling approach.

• Clarity

  4/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  The description gives concrete real-world examples, names the DEM and imagery sources, and specifies the modelling methods and the inundation-mapping output, so the deliverable is well defined even though the physics is demanding.

• Acceptance potential

  3/5

  Middle of the pack. This statement will not win the room for you — you will have to.

  The demo is compelling and the data is free, but flood hydrodynamics is specialist CFD where correctness matters, validation without observed data is weak, and an NTRO or disaster-domain judge will ask how the model was verified — so a visually convincing but physically unvalidated simulation is the risk.

• Effort

  Massive

  A semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.

  Terrain preprocessing, breach modelling, a numerically stable hydrodynamic solver over real DEM data, and inundation mapping with scenario comparison is a large effort dominated by getting the fluid dynamics right.

• Demo-ability

  Easy

  Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

  A flood wave animating down a real valley with the inundation map growing over time is a genuinely striking, self-explanatory disaster-response visual.

The demo they will have already seen 🪞

Somewhere around 130–310 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• Free DEMs and satellite imagery mean the terrain and reference data come at no cost for any river you choose
• Open hydrodynamic solvers like ANUGA and LISFLOOD-FP exist, so you can build on validated physics rather than a hand-rolled model
• The flood-wave-down-a-valley animation is one of the most viscerally compelling disaster demos available