Skip to main content
Scenario dates
Updated over 2 weeks ago

The scenario date is the date that Phoenix uses when running a model.

Exceptions to the rule

Some inputs, such as Fire History and Supplementary Wildfire History, impact the scenario date of the model. For example, if a burn was dated 01/06/24 and the scenario date was 02/06/24, it would have a different result than if the Scenario date was 01/01/25 because there have been 6 months of regrowth.

Production environment

Project Type

UI Behaviour:
Run Scenario Date

Phoenix Behaviour:
Ignition/Phoenix Start Date

Max Fuel Loads

MS: 01/01 of the next year; at point of project creation.

MS: 01/01 of the next year; at point of project creation.

Snapshot

CR: Date of the input file: ‘Modified Fire history’ (listed in the file name)

CR: 01/01 of the next year; relative to Modified Fire History.

AWP Forecast

FM: Defaults set to: 01/01 of the next year; at point of project creation.

You can change with the date picker.

01/01 of next year, after the UI date picker (left)

Rule:

Period: 02/01/YYYY – 01/01/YYYY

Phoenix reverts to: next 01/01 (the final day of period)

  • If UI date is 01/01/2025

    • then 01/01/2025 is used for Phoenix

  • If UI date is 02/01/2025

    • then 01/01/2026 is used for Phoenix

  • If UI date is 15/07/2025

    • then 01/01/2026 is used for Phoenix

AWP Evaluation

PM:

Fixed to what was used on Authorised Snapshot Reference run. You cannot edit this date.

Fixed to what was used on the Authorised Snapshot Reference run.

  • If UI date is 01/01/2025

    • then 01/01/2026 is used for Phoenix

  • If UI date is 02/01/2025

    • then 01/01/2026 is used for Phoenix

  • If UI date is 15/07/2025

    • then 01/01/2026 is used for Phoenix

BFRMP

CR: 01/01 of the next year; at point of project creation.
FR & FT: Current Risk (CR) scenario date +5 years.

CR: 01/01 of the next year; at point of project creation.
FR & FT: Current Risk (CR) scenario date +5 years.

Modelled Impact Time

MS: Defaults set to:

01/01 of the next year; at point of project creation.

You can change using the date picker (at each run). The date picker is limited to the following options:

  • Past: 01/01/2000 (inclusive)

  • Future: 31/12/2090 (inclusive)

You can only edit FB runs, not IA runs.

MS: Date set in the date picker.

Individual Treatment Comparison

RR: 01/01 of the next year; at point of project creation.

RT: 01/01 of the next year; at point of project creation.

RR: 01/01 of the next year; at point of project creation. (inherited from UI)
RT: 01/01 of the next year; at point of project creation. (inherited from UI)

Brigade Treatment Comparison

RR: 01/01 of the next year; at point of project creation.

RT: 01/01 of the next year; at point of project creation.

RR: 01/01 of the next year; at point of project creation. (inherited from UI)
RT: 01/01 of the next year; at point of project creation. (inherited from UI)

RMP Sandbox differences

The following table shows which project types have different scenario date rules in the RMP Sandbox.

Project Type

UI Behaviour:
Run Scenario Date

Phoenix Behaviour:
Ignition/Phoenix Start Date

Max Fuel Loads

MS: Defaults set to: 01/01 of the next year; at point of project creation.

You can change with the date picker.

01/01 of next year, after the UI date picker (left)

Rule:

Period: 02/01/YYYY – 01/01/YYYY

Phoenix reverts to: next 01/01 (the final day of period)

  • If UI date is 01/01/2025

    • then 01/01/2025 is used for Phoenix

  • If UI date is 02/01/2025

    • then 01/01/2026 is used for Phoenix

  • If UI date is 15/07/2025

    • then 01/01/2026 is used for Phoenix

Statewide:
AWP Evaluation

PM: Defaults set to: Scenario date of the Authorised Snapshot reference run.

You can change with the date picker.

01/01 of next year, after the UI Datepicker (left)

Rule:

Period: 02/01/YYYY – 01/01/YYYY

Phoenix reverts to: next 01/01 (the final day of period)

  • If UI date is 01/01/2025

    • then 01/01/2025 is used for Phoenix

  • If UI date is 02/01/2025

    • then 01/01/2026 is used for Phoenix

  • If UI date is 15/07/2025

    • then 01/01/2026 is used for Phoenix

BFMC:
BFRMP

CR: Defaults set to: 01/01 of the next year; at point of project creation.

You can change with the date picker.

FR & FT:

  • CR scenario date PLUS # year(s):

    • Choose ‘# year number’ from options:

      • Dropdown selector, with options:

        • 1, 2, 3, 4, 5, 10, 15, 20, 25, 30 etc

        • in 5’s increments

        • up to 90 (if possible, as far in the future as possible).

      • Or,

      • Numeric input

        • Can be any number between 1 - 90

  • Defaults set to:

    CR scenario date +5 years (same as prod).

01/01 of next year, after the UI Datepicker (left)

Rule:

Period: 02/01/YYYY – 01/01/YYYY

Phoenix reverts to: next 01/01 (the final day of period)

  • If UI date is 01/01/2025

    • then 01/01/2025 is used for Phoenix

  • If UI date is 02/01/2025

    • then 01/01/2026 is used for Phoenix

  • If UI date is 15/07/2025

    • then 01/01/2026 is used for Phoenix

Did this answer your question?