Skip to main content
Fire Behaviour configurations

List of all Fire Behaviour configurations in the RMP.

Updated over a week ago

Permissions: Only certain user roles can view and edit data in Settings.

You can freely configure ignition and scenario dates in the RMP Sandbox. For more information, see the RMP Sandbox documentation.

Statewide project setup

Configuration

Phoenix XML name

Description

Can you change the defaults?

Can you override the default at a ?

Location in RMP

Max Fuel Loads scenario date

01/01 of the following year (from when you create the project)

No

No

Default

Settings > Configurations > Fire Behaviour > Statewide project setup

Snapshot scenario date

Date of the Modified Fire history file

No

No

Default

Settings > Configurations > Fire Behaviour > Statewide project setup

Ignition point start time

Start_Time

Default time: 11:00

No

No

Default

Settings > Configurations > Fire Behaviour > Statewide project setup

Ignition point duration

End_Time

Default time: 23:00

No

No

Default

Settings > Configurations > Fire Behaviour > Statewide project setup

BFRMP project setup

Configuration

Phoenix XML name

Description

Can you change the defaults?

Can you override the default at a ?

Location in RMP

Current scenario date

01/01 of the following year (from when you create the project)

No

No

Default

Settings > Configurations > Fire Behaviour > BFRMP project setup

Future scenario date

Current scenario date plus five years

No

No

Default

Settings > Configurations > Fire Behaviour > BFRMP project setup

Ignition point start time

Start_Time

Default time: 11:00

No

No

Default

Settings > Configurations > Fire Behaviour > BFRMP project setup

Ignition point duration

End_Time

Default time: 23:00

No

No

Default

Settings > Configurations > Fire Behaviour > BFRMP project setup

Local project setup

Configuration

Phoenix XML name

Description

Can you change the defaults?

Can you override the default at a run level?

Location in RMP

Modelled Impact Time scenario date

01/01 of the following year (from when you create the project)

No

No

Default

Settings > Configurations > Fire Behaviour > Local project setup

Individual Treatment Comparison scenario date

01/01 of the following year (from when you create the project)

No

No

Default

Settings > Configurations > Fire Behaviour > Local project setup

Brigade Treatment Comparison scenario date

01/01 of the following year (from when you create the project)

Ignition point start time

Start_Time

Default time: 11:00

No

No

Default

Settings > Configurations > Fire Behaviour > Local project setup

Ignition point duration

End_Time

Default time: 23:00

No

No

Default

Settings > Configurations > Fire Behaviour > Local project setup

Fire Danger Rating (FDR)

Configuration

Description

File type

Location in RMP

Fire Danger Rating system (FDR)

Based on the NSW FDR system (not AFDRS). These are set at 3 decimal places.

BFRMP projects:

  • Compulsory configuration (specific to each project)

  • You can edit it any time in the Current Risk scenario (not after this)

Statewide projects:

  • The RMP pulls the FDR configurations set in Weather Regions and applies them to runs

Local projects:

  • The RMP pulls the FDR configurations set in Weather Zones and applies them to runs

N/A

BFRMP projects:

  • Project setup

  • Current Risk scenario run settings

Statewide projects:

  • Set in Weather Regions (Settings > Weather Regions)

Probability of FDR and probability of ignition by FDR

Used to calibrate the likelihood and consequence for risk calculations.

.json

Phoenix RapidFire

Configuration (Phoenix setting)

Phoenix XML name

Default setting

Can you change the defaults?

Can you override the default at a run level?

Location in RMP

Simulation type

SimulationType

General

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Resolution

GridResolution

180

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Sensitivity

SensitivityType

None

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Time Offset

WeatherOffset

blank

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Final Image

ExportGridPNG

unticked

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Grid Shapefile

ExportGridSHP

tick

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Spotting - Time step policy

SpotTimeStepPolicy <Value_1>

Dynamic

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Static time step

SpotTimeStepPolicy <Value_2>

blank

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Grass curing coefficient equation

GrassCuringCoefEquation

Cruz et al (2015)

Yes

Yes

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Special Behaviour

120

No

No

Default

Settings > Configurations > Fire Behaviour > Phoenix RapidFire

Impact Analysis configurations

Assets (Vulnerability and Cost & Recovery)

Configuration

Description

File type

Categories

Can you change the defaults?

Can you override at a run level?

RMP location

Assets- Vulnerability Curve Values

  • For each asset type, a matrix of percentage values describes the default statewide probability of escalating Impact levels for escalating fire Exposure levels.

  • These vulnerability curve values are integrated with the summarised Phoenix outputs to provide the initial risk assessment for each asset type.

  • Each exposure row must add up to 100%.

  • Each asset vulnerability curve will fall under an Asset group (e.g. Fencing curve is in Agriculture group).

  • Each input asset will be assigned a Vulnerability Curve (e.g. Ag_Fencing is assigned Fencing curve values)

  • A curve can be assigned to multiple input assets, but each asset can only be assigned to one curve.

Note: Only certain RMP Amin users can edit these settings.

.json

  • Exposure

    • None

    • Ember

    • Flame <2

    • Flame 2-10

    • Flame >10

  • Impact

    • None

    • Minor

    • Major

    • Destroyed

Yes

Yes

Default

Settings > Configurations > Assets - Vulnerability

Assets - Cost & Recovery

  • For each asset type, a matrix of dollar cost per unit for each Impact category. The unit depends on the feature type of the asset, see categories.

  • Each asset type also has a recovery time factor and a cost multiplier.

  • When setting Cost & Recovery, available values depend on the .shp file type:

    • Points:

      • Each

      • per 180m2 grid

    • Lines:

      • Each

      • per km

    • Polygons:

      • Each

      • per hectare

      • per 180m2 grid

Note: Only certain RMP Amin users can edit these settings.

.json

  • Impact

    • None

    • Minor

    • Major

    • Destroyed

  • line

    • $ per kilometre

  • point

    • $ per whole unit (ie each)

    • $ for one per cell (ie only count one per cell)

  • polygon

    • $ per hectare, or

    • $ per 180m2 grid, or

    • $ per whole unit (EH to confirm with Katie)

Yes

Yes

Default

Settings > Configurations > Assets - Cost & Recovery

Classification

Configuration

Description

File type

Category values

Can you change the defaults?

Can you override at a run level?

Location in RMP

Times Burnt (raster categorisation values)

Classification ranging from Lowest to Highest to classify and visualise the Times Burnt raster. No Impact = 0

.json

Category values

  • Lowest Frequency

  • Low Frequency

  • Moderate Frequency

  • High Frequency

  • Highest Frequency

Yes

Yes

Default

Settings > Configurations > Impact Analysis > Classification > Raster classification values

Residential Risk (raster categorisation values)

Residential risk classification from Lowest to highest. No Impact = 0

.json

  • Lowest Risk

  • Low Risk

  • Moderate Risk

  • High Risk

  • Highest Risk

Yes

Yes

Default

Settings > Configurations > Impact Analysis > Classification > Raster classification values

Economic Risk (raster categorisation values)

Economic risk classification from Lowest to Highest. No Impact = 0

.json

  • No impact

  • Lowest Risk

  • Low Risk

  • Moderate Risk

  • High Risk

  • Highest Risk

Yes

Yes

Default

Settings > Configurations > Impact Analysis > Classification > Raster classification values

Did this answer your question?