Results: Section Guide

The Results section is only relevant to users who have successfully run Batch Configs in the Scenarios section. It therefore also requires the user workspace to be set up.

Purpose of the Results section

The Results section enables summarisation and visualisation of output from HEM simulations successfully run in the Scenarios section, and stored in the output folder in the user workspace. The Config dropdown lists saved Batch Configs. Metrics and graphs are available only when matching output files exist.

View Config inputs

Selecting a Batch Config from the Config dropdown shows all permutations from that Config in the Inputs table. This table is horizontally scrollable, and the section is expandable, to show the parameter variations for each created scenario.

Outputs by Wrapper

Output files depend on the model_wrappers and additional_outputs parameters set in the Batch Config for that specific model.

Core

The passthrough parameter runs the model as-is without modifications.

Use case: Standard operational energy analysis

Outputs: results.csv (detailed half-hourly), results_summary.csv (annual summary), results_static.csv

FHS Assumptions

The fhs_assumptions wrapper applies FHS preprocessing, including standardised occupancy, gains, and schedules. It runs a single calculation rather than the full compliance suite.

Use case: Core calculation comparable to FHS compliance "actual" values

Outputs: Same as Core, but with FHS-standardized assumptions and FHS-comparable results_summary.csv

FHS Compliance

The fhs_compliance wrapper runs multiple calculations:

• FHS actual with FHS assumptions
• FHS FEE (Fabric Energy Efficiency)
• FHS Notional A and B
• FHS Notional FEE A and B

Use case: Full FHS compliance assessment

Outputs: fhs_compliance_report.json (main report) + multiple result sets

The Results section checks which expected output files are actually present for the selected Batch Config and selected models. Metrics and graphs that depend on an output file that is not present may be hidden or unavailable until the relevant simulation output exists. Compliance metrics are shown when a compliance output is available.

Detailed Core Outputs

For Core (passthrough or fhs_assumptions) model runs, the additional_outputs parameter creates optional postprocessing outputs:

Heat Balance

The heat_balance toggle produces three CSV files showing heat flows at different boundaries:

• results_heat_balance_air_node.csv: air node heat balance, including solar gains, internal gains, heating/cooling system gains, energy to change internal temperature, thermal bridges, infiltration/ventilation losses, and fabric heat loss
• results_heat_balance_internal_boundary.csv: internal fabric boundary results, including fabric-air convective heat transfer, solar gains to fabric, internal gains to fabric, and heating/cooling system gains to fabric
• results_heat_balance_external_boundary.csv: external boundary results, including fabric losses to external air, solar gains on external surfaces, sky radiation losses, and ground losses

Detailed Heating Cooling

The detailed_heating_cooling toggle produces detailed per-timestep outputs for heating and cooling systems:

• results_heat_source_wet__<name>.csv: heat pump or boiler per-timestep results, including service name, type, on/off status, energy required, temperatures, CoP, operating conditions, run time, load ratio, delivered energy, input energy, and operating mode
• results_heat_source_wet_summary__<name>.csv: annual summaries for wet heat sources
• results_emitters_<name>.csv: detailed emitter results
• ventilation_results.csv: air flow rates, mass flows, pressure differences, and air changes per hour (ACH)
• results_hot_water_source_summary__<name>.csv: hot water system summaries
• results_esh_<name>.csv: electric storage heater results

View, Edit and Create metrics

Metrics are aggregations of specific columns in output files. Metrics are stored in JSON format files in the user workspace under input/analytics.

Common metric fields include:

• resultsKey: the result source key, such as results or results_heat_balance_air_node; if omitted, results is used.
• label: the auto-generated label shown for the metric
• column: the column in the output file aggregated for the metric
• functype: the metric type, such as sum, average, peak, min, cost, sumIf, averageIf, countIf, or compliance
• comparator: used for sumIf, averageIf, and countIf; can be >, >=, <, <=, or =
• threshold: number used for conditional metrics, defaulting to 0

Cost metrics require retailer and tariff. Conditional metrics require comparator and threshold. Compliance metrics use JSON rather than CSV.

The default metrics config is input/analytics/default_metrics.json. Some batch configs may also have their own metrics file in input/analytics.

Metrics can be viewed in the Summary Table or in Graphs by clicking files in the Inputs table. Every metric in the Summary table has a detailed Graph. Clicking Add metric on the Summary table, or clicking the + button, allows metrics to be added to the analytics config. Metrics can be edited within their Graphs.

When creating or editing a metric, choose the result source that contains the column you want to analyse. The default source is results.csv; optional outputs such as heat balance, detailed heating/cooling, or ventilation results only appear when those files exist for the selected run.

Graphs can be zoomed by dragging over a range, and reset by double clicking. The aggregation shown on the graph changes to reflect the zoom range.

Edit Tariffs

Tariffs are saved in the input/tariff_data_structured folder in the user workspace. Each retailer creates a CSV file, with each tariff as a column in that file.

Tariffs can be created or edited using the Tariffs modal near the top right of the tab.

Export Results

Use Export to download:

• the Inputs table, listing the scenarios and permutations in the selected Config
• the Metrics table for the selected models
• the currently open graph as a CSV file