{% extends "base.html" %} {% block title %} » Scenarios {% endblock %} {% block nav %} Scenarios [add] {% endblock %} {% block content %}

Scenarios

{% for scenario in scenarios %} {% endfor %}
Scenario Run View Edit Scenario Start Year Scenario Start Month Scenario Duration
{{scenario.name}} Run View [edit] {{scenario.props.scenario_start_year}} {{scenario.props.scenario_start_month}} {{scenario.props.scenario_duration}}

Notes

HH Data

Default forecasting

Before the forecast_date Chellow uses data in the database (if any), and after that date it uses data from the same month but in the year before the forecast_date.

If a rate script isn't found for a particular date, then the most recent rate script is used.

Virtual bills can include TRIAD estimates and actuals in a variety of ways. For example, a virtual bill may use TRIAD estimates for all months until triad dates are available for that financial year, in which case it switches to using the actual TRIAD for March.

TRIAD estimates are calculated using the actual TRIAD from the latest historical year for which we have TRIAD dates. Historical kW and status are used, together with current LAFs and TRIAD rates, with the result apportioned throughout each month.

Applying HH data in the scenario runner

Taking 'generated' as an example, for each half-hour Chellow will calculate the difference between the scenario_generated and the existing_generated. If scenario_generated >= existing_generated then any imported_net will be reduced first, then exported_net will be increased until all the difference is exhausted. Otherwise if scenario_generated < existing_generated then exported_net will be reduced first, and then imported_net will be increased. A similar approach is taken with used, parasitic and gen_net kWh.

The method is the same for months after the forecast_date but with the existing_generated being found from the default forecast.

{% endblock %}