BREACHER COMMAND FILE AND BATCH FILE
Included with Breacher and Breacher-Post are example set up files. Dam and breach parameters are specified in the Breacher command file and run by “calling” the command file and the Breacher executable with a batch file. See Figure 1and Figure 2.
It’s recommended to save the Breacher executable to the following path:
"C:\BREACHER\2024-01-beta.01\breacher.exe"
Breacher's Workflow
The water balance model’s workflow for Breacher is shown in Figure 3.
Simulation Controls - Comprehensive Mode
Comprehensive mode can be triggered with the following command: Breach_Mode = " Comprehensive "
Comprehensive mode uses the dam characteristics in the command file to look up the dam with the closest match in (Azmi and Thomson, 2024). The focus of this lookup is predominantly height of breach (hb) and volume of water (Vw). It’s recommended to sensitivity test this lookup by changing inputs like Dam_Type and Dam_Erodibility to see if others match.
Secondly, Comprehensive Mode also compares inputs and results from the command file to common literature. Average width from the literature is translated to bottom width with the side slope specified in the control file, it should be noted publications on breach parameters and peak flow (ie Froehlich’s work) often specify side slope too. It may be beneficial to the Breacher modeller to review the relevant literature for their associated side slopes and other assumptions and limitations prior to selecting breach parameters.
SIMULATION CONTROLS - Detailed Output Mode
Detailed output mode can be triggered with the following command: Breach_Output = "Detailed"
Turning on this command allows for writing storage level, outflow and other outputs from the Breacher simulation for each simulated event. Caution should be used when turning this on for a lot of events as, for example, running 10,000 simulations with this turned on will create 10,000 files. Turning this command off and running large quantities of simulations will still write critical outputs (ie peak flow) to the summary.bsf file.
Simulation Controls - Breach parameters
All parameters required for a simulation, without turning on Comprehensive Mode, are shown in Figure 7.
[x, y] indicates a lower and upper value for a parameter to be randomly chosen.
It’s important to check there isn’t overlap between parameter ranges that do not make sense, for example Breach_Base above Top_of_Dam, as this could create unusual results.
SIMULATION CONTROLS - Databases (dbase)
Databases required for a simulation, without turning on Comprehensive Mode, are shown in Figure 8.
It’s recommended the headers and format in the templates provided be retained, to reduce the risk of model errors. Where inflow is not required, inflow rates can be set as 0.
It’s recommended the max height and storage in elev_storage.csv be set above the Failure_WSL, and lowest height and storage be set below Breach_Base.
Simulation Controls - Comprehensive Parameters
Extra parameters required for a simulation, when turning on Comprehensive Mode, are shown in Figure 9.