Storm Injector Help

The events that can be selected can be categorised as either Standard or Custom Events.

 

Standard Events

Standard events include Point Temporal Patterns, Areal Temporal Patterns and ARR1987 Temporal Patterns. You can add Point, Areal (assuming Areal TPs are loaded) and ARR1987 events at the same time and compare the results.

Standard Events (63.2% - 1% AEP), Very Frequent or Rare Events can be accessed via the checkboxes to the right.

Typical event / temporal pattern classification configurations are highlighted in light blue and can be selected automatically via right click menu. The secondary bin are highlighted in gray and can also be accessed via right click menu. More information regarding using multiple bins can be found in the How To section's Using Temporal Patterns from Multiple Bins.

The Prefix field allows some text to be added the start of all event labels. This can be useful when comparing results from multiple projects which can be done by loading multiple run lists.

A more detailed how to guide related to using Prefixes to compare scenarios can be found here.

 

Point TP Events

 

 

Areal TP Events

 

ARR1987 TP Events

Select the recurrence interval and TP Zone combinations to be modelled. ARR1987 storm use the following parameters:

•IFD values based on an *ARR87* IFD Location.

•Pervious loss rates (IL/CL) as per the ARR 87 Pervious Losses box in the settings tab

•Impervious Losses as per the Impervious Losses (ARR2016 and ARR1987) box in the settings tab

•ARF (depth-area ratios) based on Figure 1.6 ARR 87 approximated by polynomial.

•Temporal Patterns from ARR 87 Vol 2 Table 3.2

 

 

Durations

You can customise which durations are to be modelled in the Durations tab. Individual durations can be checked or unchecked and the right click menu can automatically check or uncheck durations longer or shorter than a user specified value.

 

Custom Events

Custom Events are typically used for sensitivity analysis for partial area, rainfall increase, initial loss uncertainty and climate change. They can also be used to apply the growth curves for events rarer than 1% AEP and durations < 24 hours. Custom Events can be renamed to suit the user's preferences by appending $Name$ to the end of the custom event (that is, the new name book-ended by the $ character.

 

For example, the estimation of rarer than 1% AEP events using the growth curves in Table 8.3.2 (Section 3.6.3 Book 8) can be accommodated using the following Rainfall Increase custom events and renamed as follows:

•RInc_1% AEP_14.0_rare$200YrARI$

•RInc_1% AEP_34.4_rare$500YrARI$

•RInc_1% AEP_51.3_rare$1000YrARI$

•RInc_1% AEP_69.8_rare$2000YrARI$

*Growth curve approaches are now superseded since October 31st 2018 when the BoM released rare IFD depths for durations < 24 hours.

 

In the Custom Event format, the event description is always the 2nd field (underscore delimiter). To access frequent or rare IFD events, simply use their event descriptors such as '1 in 1000' or '12EY'. To access ARR 1987 events, use their descriptors such as '100 Yr'.

More information on the types of custom events available is shown below.

 

Partial Area Checks

Partial Area Checks (PAC) are useful to investigate the effects of differing ARFs related to different areas of interest. For example, if your entire rainfall runoff model catchment is 100 km2 (and this was entered in the Catchment Details panel) and yet you are also interested in the results of a subcatchment in your model that has a catchment of 50 km2, then you may consider including a 50 km2 PAC. This will allow you to quantify the difference in runoff due to the change in ARF. In this example, total rainfall depth would be about 4% higher for the 1% AEP, 24hr event with ARR 2016.

•A PAC for a point temporal pattern example is: PAC_1% AEP_50_rare which would indicate a PAC with ARFs based on 50 km2 area for the rare temporal patterns.

•A PAC for a areal temporal pattern example is: PAC_1% AEP_50_100 which would indicate a PAC with ARFs based on 50 km2 area for the 100km2 reference area temporal pattern.

•A PAC for a point temporal pattern example is: PAC_100 Yr_50_ARR87Z1 which would indicate a PAC with ARFs based on 50 km2  for the 100 Yr event with ARR 1987 temporal patterns for Zone 1.

 

Rainfall Increase Sensitivity Analysis

To enter a hard-coded rainfall increase event, enter a code of the form RInc_AEP_Increase/(-)Decrease(%)_temporal pattern classification (eg., rare for point temporal patterns or reference area for areal temporal patterns.

•A point temporal pattern example is: RInc_1% AEP_20_rare which would indicate a 20% rainfall increase for the 1% AEP for the rare temporal patterns.

•An areal temporal pattern example is: RInc_1% AEP_20_100 which would indicate a 20% rainfall increase for the 1% AEP for the 100km2 reference area temporal pattern.

•An ARR 87 example is: RInc_100 Yr_20_ARR87Z1 which would indicate a 20% rainfall increase for the 100 Yr event with ARR 1987 temporal patterns for Zone 1.

 

Pervious Initial Loss Sensitivity Analysis

To enter an adjustment to the net previous initial loss rate, enter a code of the form ILInc_AEP_Increase/(-)Decrease(%)_temporal pattern classification (eg., rare for point temporal patterns or reference area for areal temporal patterns.

•A point temporal pattern example is: ILInc_1% AEP_-20_rare which would indicate a 20% initial loss decrease for the 1% AEP for the rare temporal patterns.

•An areal temporal pattern example is: ILInc_1% AEP_-20_100 which would indicate a 20% initial loss decrease for the 1% AEP for the 100km2 reference area temporal pattern.

•An ARR 87 example is: ILInc_100 Yr_-20_ARR87Z1 which would indicate a 20% initial loss decrease for the 100 Yr event with ARR 1987 temporal patterns for Zone 1.

 

Climate Change Chapter in ARR

To enter an Climate Change Considerations event (CCC), you can enter a custom event with 7 parameters delimited by '_':

•CCC

•Event Code (eg 1% AEP for Point/ Areal, 100 Yr for ARR87)

•Temp Change (can be a discrete number of degrees, or a SSP code like SSP4-8.5-2060-Median, SSP4-8.5-2060-Low or SSP4-8.5-2060-High - SSP codes 1-4 and for 2040, 2060 and 2100 are included). Discrete temperature predictions for a SSP can be applied automatically via right-click from the Climate Change panel as discussed below.

•Rate of Change (can be a discrete number of % per degree, or Median, Low, High to use the rate of change from Tables 1 and 1A. Low and High refer to the +/- 33% likely range)

•Initial Loss Adjustment (can be a discrete number of % adjustment (not per degree), or the words: Median, Low, High to use the values from Table 4 for the Region combined with change in temperature. You can also use a specific region name, such as Southern Slopes (mainland) to use the median for this region. This can be useful if applying to ARR87 custom events.

•Continuing Loss Adjustment (can be a discrete number of % adjustment (not per degree), or the words: Median, Low, High to use the values from Table 4 for the Region combined with change in temperature. You can also use a specific region name, such as Southern Slopes (mainland) to use the median for this region. This can be useful if applying to ARR87 custom events.

•Classification String (the temporal pattern bin for Point TPs (eg rare), the area bin for Areal TPs (eg 100) or ARR87Z1 (eg for Zone 1 ARR87)

 

Climate Change custom events can also be created by right-clicking on a temperature prediction in the Climate Change panel. The event will be configured with the settings in the Rate of Change, Initial Loss Changes and Continuing Loss Changes combo boxes to the right of the panel.

 

Note that for the temperature ranges in ARR (see below), the Data Hub applies these values at the midpoint of their range, so SSP4-8.5-2060-Median will be equivalent to the Data Hub temperature for 2050. This is why the 2030, 2050 and 2090 rows in the Climate Change panel above are bold.

 

 

An example for point temporal patterns is: CCC_1% AEP_SSP2-4.5-2040-Median_Median_Median_Median_rare$1pcAEP-CC2040$ which would apply a median rainfall depth adjustment based on 1.3 degrees (SSP2-4.5-2040) of warming (compared to 1961-1990 baseline) with the median rate of rise (which is duration dependent., 8-15 % per degree) and median changes (typically increases) in initial and continuing loss rates. Uncertainty analysis could be undertake by changing Median to High or Low but keep in mind that High and Low with reference to loss rates are typically refering to increases in loss rates.

 

In general, to keep text as short as possible, Median, Low and High can be substituted with M, L and H respectively. For example, CCC_1% AEP_SSP2-4.5-2040-M_M_M_M_rare$1pcAEP-CC2040$

 

Examples for Areal and ARR87 temporal patterns are:

CCC_1% AEP_SSP2-4.5-2040-Median_Median_Median_Median_100$1pcAEP-CC2040$

CCC_100 Yr_SSP2-4.5-2040-Median_Median_Southern Slopes (mainland)_Southern Slopes (mainland)_ARR87Z1$100Yr-CC2040$ 

 

Please note that the rainfall depth adjustments via temperature change and rate of change are also available through the Cstm events for use with the PMP/PMF for example.

 

Custom Temporal Patterns and Events (including PMF)

 

Detailed instructions for PMP/PMF events can be found in the PMP/PMF Modelling Section.

 

A general example of a custom temporal pattern event is as follows:

 

CStm_TPName_1%_1% AEP_HUB DATA_0_0_1.0$EventName$

 

This can be broken down (underscore separated) as follows:

•CStm: this tag informs Storm Injector that we are applying a set of custom temporal pattern for various durations as listed in the Custom Temporal Patterns panel on the settings tab

•TPName: this should match the first column in the Custom Temporal Patterns panel on the settings tab. From v1.3.9, you can also access ARR Point, ARR Areal and ARR87 temporal patterns in the project using names consistent with these examples, *ARR Point-East Coast (South)-rare*, *ARR Areal-East Coast (South)-100*, *ARR87-Zone 1-Less than 30 Years*

•1%: this is the column header for the rainfall depth for the various durations for all IFD Locations (it is important that all IFD Locations selected in the IFD Location column in the Project Setup tab have a depth column with a matching header). If the rainfall column exists in an IFD Location with an IFD Suffix (eg *Rare*, *VeryFrequent*, *ARR87* or HIRDS suffixes such as *NZ-RCP8.5-2050*), then this suffix should be added after the column header, eg 1 in 2000*Rare*.

•1% AEP: this tag relates to the Initial Loss (pervious) that should be applied. It can be a ARR2019 event name (to use the IL from the Storm Burst loss table), ARR87 to use the ARR87 initial loss from the settings tab or a specific numerical value

•HUB DATA: this tag relates to the Continuing Loss that should be applied. It can be HUB DATA to use the value from the ARR DATA HUB or ARR87 to use the ARR87 continuing loss from the settings tab or a specific numerical value

•0: Any depth adjustment, for example 20 would be a 20% increase. The draft climate change considerations can also be accessed here via two parameter separated by the '#' symbol The first should be temperature change (can be a discrete number of degrees, or a SSP code like SSP4-8.5-2060-Median, SSP4-8.5-2060-Low or SSP4-8.5-2060-High - SSP codes 1-4 and for 2040, 2060 and 2100 are included. The second should be the rate of change (can be a discrete number of % per degree, or Median, Low, High to use the rate of change from Tables 1 and 1A. Low and High refer to the +/- 33% likely range). An example for this parameter is: SSP4-8.5-2060-Median#Median

•0: Any IL adjustment, for example -20 would be a 20% decrease

•1.0: The ARF to apply. It can be a ARR2019 Event name to use the value from the Areal Reduction Factors table or a specific value. A value of 1.0 means no ARF adjustment will be applied. ARR87-Zone5 or ARR87-NonZone5 tags can also be used to apply ARR 1987 style ARFs.

•$EventName$: Event renaming, in this example the event should be named PMF GSDM.

 

The Cstm custom event can be used to apply temporal patterns that are not included with Storm Injector by:

•Exporting the Custom Temporal Patterns table from the Settings tab to CSV which can then be edited in Excel

•Adding the relevant temporal patterns to the table

•Saving the CSV and re-importing to Storm Injector.

 

The default custom temporal patterns can be restored via right click >> Restore Defaults

 

Once the appropriate events have been selected, the storms can be created.