The Results section is only relevant to users that have successfully run Batch Configs in the Scenarios section. It therefore also requires the user workspace to be set up.
Purpose of 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. Only Batch Configs with expected outputs can be selected from the Config dropdown.
View Config inputs
Selecting a Batch Config from the Config dropdown will result in all permutations from that Config being displayed 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 will depend on the model_wrappers and additional_outputs parameters set in the Batch Config for that specific model. Based on the model_wrappers:
Core
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
fhs_assumptions wrapper
Applies FHS preprocessing (standardized occupancy, gains, schedules). Runs a single calculation (not 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
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
Detailed Core Outputs
In addition, for Core (passthrough or fhs_assumptions) model runs the additional_outputs parameter creates additional outputs during postprocessing:
Heat Balance
heat_balance toggle
Produces 3 CSV files showing heat flows at different boundaries:
Air node heat balance (results_heat_balance_air_node.csv)
Solar gains, internal gains, heating/cooling system gains
Energy to change internal temperature
Thermal bridges, infiltration/ventilation losses
Fabric heat loss
Internal fabric boundary (results_heat_balance_internal_boundary.csv)
Fabric-air convective heat transfer
Solar gains to fabric
Internal gains to fabric
Heating/cooling system gains to fabric (thermal mass interactions)
External boundary (results_heat_balance_external_boundary.csv)
Fabric losses to external air (convective and radiative)
Solar gains on external surfaces
Sky radiation losses
Ground losses
Detailed Heating Cooling
detailed_heating_cooling toggle
Produces detailed per-timestep outputs for heating and cooling systems:
Heat pump/boiler per-timestep results (results_heat_source_wet__<name>.csv)
Service name, type, on/off status
Energy output required, temperatures, CoP, operating conditions
Time running (full/part load), load ratio
Energy delivered (HP, backup, total)
Energy input (HP, backup, pumps, fans, total)
Operating modes (on/off, standby, etc.)
Annual summaries (results_heat_source_wet_summary__<name>.csv)
Emitter detailed results (results_emitters_<name>.csv)
Ventilation detailed results (ventilation_results.csv) - including air flow rates, mass flows, pressure differences, air changes per hour (ACH)
Hot water system summaries (results_hot_water_source_summary__<name>.csv)
Electric storage heater results (results_esh_<name>.csv)
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 CSV file the results are read from. If empty, the default results CSV is used.
label: The auto-generated label shown for the metric
column: The column in the output file aggregated for the metric
functype: Selects metric type:
sum: sum of all values
average: mean of all values
peak: maximum value
min: minimum value
cost: cost calculation (requires retailer and tariff)
sumIf: sum only when condition is met (requires comparator and threshold)
averageIf: average only when condition is met (requires comparator and threshold)
countIf: count rows when condition is met (requires comparator and threshold)
compliance: compliance metrics (uses JSON, not CSV)
comparator: used for sumIf, averageIf and countIf, can be >, >=, <, <= or =
threshold: number used for conditional metrics, defaults to 0
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.
Graphs can be zoomed into by dragging on a range, and reset by double clicking. The value of the aggregation 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.
Example tariffs for Octopus Energy are provided with the Sample Library. Tariffs can be created or edited using the Tariffs modal near the top right of the tab.
Export Results
The Inputs table (listing all Scenarios in the Config), the Metrics table, as well as any Graph can be exported as a CSV file download.