There are various settings available on the Settings tab. The Settings can be saved for use as future defaults using the 'Save Default Settings' button.
Most settings are self explanatory, however, the more important ones are:
Some of the important general settings are:
•Very Short Duration Events
No temporal patterns are included in the ARR Data Hub for durations of 5 mins or shorter. If this checkbox is selected then Storm Injector will create storms with 1 time step equal to the duration and deposit 100% of the rainfall depth in that timestep.
•Pause between model runs
For hydraulic models that require hardware dongles to run (particularly network dongles), it may be necessary to insert a pause between model runs.
•Downloading from Web
The Show Browser checkbox determines if the web browser will wait for the user to click Ingest Data before processing the data or if it will process automatically. The loading time governs how long the program should wait before trying to read the data. If downloading data is causing errors or you have a slow connection, you should try entering a larger loading time.
Users will need to enter the path of the hydrologic engine they would like to use.
In the case of XP-RAFTS, this file is called 'raftsEngW.exe'.
Also ensure that the Job Control and individual nodes are setup to export total hydrograph files (*.tot) to allow plotting of hydrographs in the software.
In the case of WBNM, it is suggested that the new slim engine is utilised. This file may be called: file wbnm_eng_w64.exe
Also ensure that WBNM is setup to export metafiles to allow hydrograph export (out_metafile=.TRUE. to allow hydrographs)
In the case of RORB, please select the command line version of the engine. This may be called RORB_CMD.exe
In the case of URBS, please select the urbs32.exe file.
There are numerous methods available to calculate the initial loss for a storm. These include using the global initial loss from the ARR Data Hub and subtracting the corresponding pre-burst depth. The user may also choose to apply the ARF to pre-burst depths prior to their subtraction from the initial loss.
The initial and continuing loss rates can also be overridden if required. Pre-burst subtractions are still made to the Override Initial Loss if selected.
The initial loss (before any pre-burst adjustment) can also be reduced by a given percentage. This is designed to allow implementation of reduced initial loss for urban catchments as per Book 5 Section 184.108.40.206.1.
Impervious loss rates are also assigned in these settings.
The user can also nominate to apply any excess pre-burst to the first timestep using the pre-burst excess options.
For advanced use, loss rates can be uniquely assigned for any AEP or subcatchment using the 'Override Global Losses' option. When this check box is selected, you will see a new panel on the Storm Generator tab that allows losses to be entered in a flexible manner. The Storm Burst Losses panel will disappear since loss rates may now vary with subcatchment.
Unique initial losses (mm), continuing loss (mm/hr), impervious initial loss (mm) and continuing impervious loss (mm/hr) can be entered in any cell using 4 comma seperated values For example: 80,5,1,0.
A hierarchy is applied to determine the loss rates to use for each subcatchment when preparing the storm files.
1.If loss rates are entered for the specific subcatchment row and specific AEP column, these are used, otherwise:
2.If loss rates are entered for the specific subcatchment row and the relevant all AEPs column (All ARR16 AEPs or All ARR87 AEPs), these are used, otherwise:
3.If loss rates are entered for the relevant impervious threshold row (based on the impervious threshold in the settings and the subcatchment impervious proportion) and the specific AEP column, these are used, otherwise:
4.If loss rates are entered for the relevant impervious threshold row (based on the impervious threshold in the settings and the subcatchment impervious proportion) and the relevant all AEPs column (All ARR16 AEPs or All ARR87 AEPs), these are used, otherwise:
5.If loss rates are entered for the 'All Subs' row and the specific AEP column, these are used, otherwise:
6.If loss rates are entered for the 'All Subs' row and the relevant all AEPs column (All ARR16 AEPs or All ARR87 AEPs), these are used.
For example, in the image shown above subcatchments with more than 0% impervious will be assigned 60 mm IL and 5 mm/hr CL where subcatchments with 0% impervious are assigned 80 mm IL and 5 mm/hr CL. The exception is Sub04 which is assigned 40 mm IL and 5 mm/hr CL. This can be further customised for individual AEPs if needed. The impervious proportion threshold used can be set in the Settings.
You can right click on this form to import and export to CSV. If you wish to work in Excel, it is recommended that you export to CSV as a first step, then edit as required in Excel and then import from CSV.
In the case of RORB, Interstation Areas are used for loss rate customisation instead of subcatchments. Also, the impervious proportion options are not available for RORB.
You should note that adjustments to these loss rate can still be made including subtraction of pre-burst depths or percentage reductions in initial loss. If you wish the loss rates in the Override Global Losses panel to be used without modification, ensure the 'Global Initial Loss' radio button is selected in the Initial Loss group box and the 'Adjust initial loss by' checkbox is not checked.
This method of customising initial and continuing loss rates is considered suitable for advanced users. It is more difficult to check the correct allocation of the loss rates since the initial and continuing loss columns in the Storms grid will now show 'override' instead of values since these values may now vary by subcatchment. Users should check the hydrologic model files generated by the 'Prepare Model Runs' step and confirm that the loss rates are correct.
If you wish to adopt specific loss rates for AEPs and subcatchments that also vary with duration (rather than using the automated pre-burst adjustments), you may wish to follow this workflow:
1.Setup the override global losses form and select the applicable durations in the Durations tab of the Selected Events panel. Prepare Models, Run Models and Save a Run List. You may also wish to save the project with a unique name at this stage or at least export the Override Global Losses form to a CSV for your records.
2.Adjust the loss rates and applicable durations and repeat as necessary.
3.When it comes time to analyse the results, you can load all the run lists together using group select or the Load List(s) >> Load more to existing list option on the Model Runs tab. You should then be able to process and analyse all results together.
Users may choose how a adopted temporal pattern for a given duration and subcatchment is selected. The options include the first exceeding the median (or median if odd number of patterns), first exceeding mean or the closest to the mean with a preference to those above the mean. For example, a bias factor of 2 would mean that a temporal pattern yielding a peak flow less than the mean would need to be half the 'distance' to the mean that the nearest result exceeding the mean before it would be selected.
For storm of durations of 1-5min, users may elect to have single timestep storms added or not using the 'Add single timestep events for 1 - 5 min checkbox.
Storm Injector allows custom temporal patterns to be input by users to apply specialised methods. The GSDM temporal pattern for the PMF is included in the section by default but others can be added. These may include specialist PMF methods such as GSAM. The easiest way to add custom temporal patterns is to right click and export to CSV. This CSV can then be edited in Excel, saved and re-imported into Storm Injector. These temporal pattern can be applied using the procedures documented in the Custom Events section.
Various utilities can be linked via the Settings to help integrate Storm Injector with other products these include:
•convert_to_ts1.exe - This utility is used to convert hydrograph output files to ts1 format for TUFLOW