Flood Modeling In The Cloud:Can it be a revolutionary cloudburst for flood analysis?
Paul RobinsonWater Resources
ManagerPaul.Robinson@ch
2m.comDr Jon Wicks
Technical DirectorFlood Modeller
2
CLOUDBURST
A cloudburst is an extreme amount of precipitation in a short period of time, sometimes accompanied by hail and thunder, that is capable of creating flood conditions.
The term "cloudburst" arose from the notion that clouds were akin to water balloons and could burst, resulting in rapid precipitation.
Swedish term "skyfall"
3
Content
• What is Cloud computing?
• How can it help me?
– Improve flood models
– Run more scenarios to enable better decisions
– Improve understanding of model confidence
– Access superior modelling power to help beat project deadlines
• What are the key benefits and issues?
4
Cloud Computing – What are we talking about?
• Using a network of remote servers hosted on the Internet to store, manage, and process data, rather than a local server or a personal computer
• Generic services:
• Amazon Web Services
• Microsoft Azure
• Intermediary services
• Parallel Works
• Flood/Water Specific
• DHI SaaS Portal
• .
5
Applying innovation to meet the needs of flood management
Advances in IT
Fast delivery & efficiency savings
Richer flood information
neededFlood Modeling
In The Cloud
6
Which software can I use?Services off the shelf:
• MIKE by DHI SaaS – broad range of solvers
• Flood Cloud
• Flood Modeller Pro 1D, 2D, 1D-2D Linked
• Flood Modeller (1D)-TUFLOW (2D)
• TUFLOW (Coming soon)
• HEC-RAS (Planned for future update)
Others in project specific settings using generic services:
• HEC-RAS
• HEC-FDA
• CityCat
• Others?
7
How to use a Cloud service for flood modelling – an exampleUser actions:
1. Set up your simulations as normal
2. ‘Click’ to run on the cloud
3. View/process results on your computer
What is actually happening:
• Automation to:
– Package input data into zip file
– Upload to cloud control server
– Distribute data and solvers to cloud resources
– Start runs, provide feedback and download results to local computer
8
An example
9
An example
10
An example
11
An example
12
An example
13
An example
14
An example
15
An example
16
An example
17
When would you use the Cloud
Examples:
• Using the Cloud to improve flood models
• Running more scenarios to enable better decisions
• Improving understanding of model confidence
• Superior modelling power to help beat project deadlines
18
Using the Cloud to improve flood models
• More calibration runs
• More validation runs
• Combined hydrology/hydraulics
• Optimisation of parameters
19
Running more scenarios to enable better decisions
Multiple scenarios can be run faster in the cloud, i.e. the run time is the same no matter how many you run
20
Richer results to enable better decisions • Traditional ‘binary’ single
return period flood map
• Truer picture of flood risk
• Spatially varying probability of flooding
• Spatially varying impacts (£,$, risk to life)
• Flood durations
• Risk attributed to defences
• Multiple sources
21
Improving understanding of model confidence
• Quantify the spatially varying confidence
• Sensitivity runs
• Monte Carlo sampling approach
• Full probabilistic analysis including defence breaches
Hydrology- Peak- shape- timing
Floodplain DTM
Channel geometry
Floodplain roughness Channel
roughness
Flood defences
In-river structures
22
Unleash modeling power to help beat project deadlines
• Continual need to deliver on improved flood risk management
• Do things better and faster
• More data, bigger models, more outputs
• The Cloud makes it easier
23
Key Benefits and IssuesBenefits Of The Cloud Issues to ConsiderFlexible and scalable to projectneeds
Building models is still a standalone exercise
Enables you to do more Debugging is still a standalone exercise
Cost effective compared to costs of setting up and maintaining a cluster of workstations
Need a careful plan for managing the huge volumes of files and data
• Selectivity in variables you save• Do you need to keep full time-series
results?Can free up existing standalone software licenses
Tends to need standard versions of software – harder to deploy project specific productivity add-ons… so far
Secure and typically more reliable
File security policies – some organizations may have strict policies on host locations
24
Other sectors using these concepts
• Climate modeling
• Manufacturing – testing designs virtually to identify issues before production
• Medical & Pharmaceutical virtual testing
• Other sectors looking to speed up testing, modeling and scenario evaluations that were limited in the past by machine and software availability.
25
What could be next?
• Increasingly streamlining services – to make them easy and intuitive to use
• Being able to access better computing resources than on your desk.
• Greater connectivity with post simulation tools – being able push to web, or dashboards etc.
• Making it easy to set up mass scenarios – potential for “auto-calibration” monte-carlo style.
• Dashboard control of “What-if” scenarios being defined by authorized stakeholders, run in the cloud, then results returned to dashboard.
26
Weather forecast
Model setup
Cloud simulations
Sensitivity tests
Post-processing
Stakeholder dashboards
Public warnings
What could be next?
• Automated workflows for multi-agency emergency responses?
• As ever though… We must think before we model!
27
Transforming the way you model www.floodmodeller.com/floodcloud
Thank You – Questions?
Upcoming webinar – ”Integrating HEC-RAS flood models within Flood Modeller Pro”: www.floodmodeller.com/webinar