TUFLOW SWMM Tutorial M04: Difference between revisions
Content deleted Content added
Chris Huxley (talk | contribs) |
Chris Huxley (talk | contribs) |
||
Line 11:
= Simulation Control Files =
TUFLOW's automated event management operates by introducing wildcard referencing into the boundary condition database.
A new control file, called the "TUFLOW Event File" is added. It lists all event titles which are applied to the wild charatcter in the boundary condition database. It also lists unique commands to associate with the specific events.<br>▼
Models are executed using a batch file, with the event specifion listed as a variable in the batch file syntax.▼
▲A new control file, called the "TUFLOW Event File" is added. It lists all event titles which are applied to the
▲Models are executed using a batch file, with the event
This tutorial example will upgrade our single simulation model to run six (six) event simulations. The simulations will cater for three (3) Annual Exceedance Probability (AEP) event magnitudes: 5%, 2% and 1% AEP (in Average Recurrance Interval (ARI) terminology, this translates to the 1 in 20, 50 and 100 year ARI events). The design storms will be simulated for two (2) event storm durations: 1 and 2 hour.▼
▲This tutorial example will upgrade our single simulation model to run six (six) event simulations. The simulations will cater for three (3) Annual Exceedance Probability (AEP) event magnitudes: 5%, 2% and 1% AEP (in Average
=== TUFLOW Boundary Condition Database (bc_dbase) ===
Line 26 ⟶ 28:
<li>Event Duration = DUR
<li>Navigate to the '''TUFLOW_SWMM_Module_04\Tutorial_Data''' folder. Copy and paste the following files to the ''' TUFLOW_SWMM_Module_04\TUFLOW\bc_dbase''' folder. These files
:*TS04_inflow_05p1hr.csv
:*TS04_inflow_05p2hr.csv
Line 40 ⟶ 42:
:*TS04_rainfall_01p2hr.csv <br>
The files with 'inflow' in their name are flow hydrograph boundary conditions sourced from an external hydrology model, such as HEC-HMS, RORB, URBS, WBNM etc. The files with 'rainfall' in their name are rainfall depth hyetographs used to define the rainfall timeseries in the SWMM urban hydrology section of the model.
<li>Save a copy of the '''bc_dbase.csv''' as '''bc_dbase_TS04_001.csv'''.
Line 66 ⟶ 69:
<font color="blue"><tt> End Time </tt></font> <font color="red"><tt>==</tt></font> <font color="black"><tt> 2</tt></font>
</ol><font color="blue"><tt>End Define</tt></font>
<li> When TUFLOW runs a simulation, it reads all of the defined events in the TEF, though only uses the event variables specified in the batch file. We will create a compatible batch file shortly.<br>
</ol>
Line 78 ⟶ 81:
<font color="green"><tt>! EVENTS</tt></font> <br>
<font color="blue"><tt>Event File </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> TS04_Event_File.tef </tt></font> <font color="green"><tt> ! Reference the TUFLOW Event File</tt></font> <br>
The location of this file in the TCF is important. If there are any commands associated with an event which overwrite other existing commands (such as End Time == in the example above), the TEF file needs to be processed last for the overwrite to occur. Referencing this file as the last line in the TCF ensures this order of
<li>Save the TCF.
</ol>
Line 134 ⟶ 137:
= Conclusion =
*Automated Event Management functionality was added to the TUFLOW SWMM model.
*Multiple event simulations were run in sequence from a batch file.
*Creation of looped batch file was demonstrated for the
*Multiple event simulation results were inspected using the QGIS TUFLOW Viewer.
<br>
| |||