Historical and Database Error Report
Overview
The Historical and Database Error Report lists the problems found when a historical run checked its generation and market data against the database. It answers one question:
Did the scenario encounter historical-data errors, and if so, which objects were affected?
The report shows the scenario's Historical Database error report (HistDBErr.csv), grouped by error type (the Remarks recorded for each row). It has no chart, time axis or chart series.
In the current Dashboard the report is the Historical & Database sub-tab of the Summary viewer. It no longer has its own chip in the Viewer Bar.
When the report contains records, the Summary sub-tab shows a warning, "Historical Database errors detected", listing each error type and its count. Click View Historical Database to open the report.
What It Is Used For
- Finding the units, sites and regions affected by historical-data problems.
- Seeing which error types were recorded, and how many of each.
- Reading the recorded values and remarks for each problem.
- Exporting an error type's table as CSV for further analysis.
When It Is Available
The Historical & Database sub-tab is available when the scenario has a Historical Database error report — either the HistDBErr.csv file in the scenario folder or the same report stored in the scenario's results file. Otherwise the sub-tab is greyed out, and its hover text explains why.
Opening the Report
- Open the Summary viewer and click the Historical & Database sub-tab in the Chart Toolbar row.
- Click View Historical Database in the warning on the Summary sub-tab.
- In the Scenarios tree, right-click the scenario and choose Load Historical DB Report (shown only for scenarios that have the report).
Report Structure
Header
| Figure | Meaning |
|---|---|
| Scenario | Name of the loaded scenario |
| Total Records | Number of rows across all error types |
| Remark Types | Number of different error types |
Error-Type Chips
Each error type has a chip, for example MaxGen Error or MREnergy Error.
- Click a chip to show or hide that error type's table.
- Right-click a chip to scroll to that table without hiding it.
- All shows every table; None hides every table.
The error types listed for a scenario are the ones present in its report; other scenarios can have different types.
Error-Type Tables
Each table has a title, its record count and an Export CSV button. Every table has these columns:
| Column | Description |
|---|---|
| Unit ID | The affected unit |
| Site ID | The site the unit belongs to |
| Region ID | The region of the site |
| Max Gen (MW) | Maximum generation recorded |
| Max Cap (MW) | Maximum capacity from the historical database |
| MR Energy (MWh) | Must-run energy from the historical database |
| Fuel Type | Fuel type, shown as a coloured badge |
| Cap Deficit (MW) | Capacity difference reported for the row |
| Remarks | The recorded error or explanation |
| Timestamp | When the row was logged |
An empty value is shown as a dash (-).
Exporting the Report
Click Export CSV on a table to save that error type's rows as a CSV file. The column headers in the file match the table, including the units.
Table Navigation
Wide tables scroll sideways. The mouse wheel scrolls a table sideways when it has no room to scroll down, and a trackpad's sideways swipe also works. Click into a table to scroll it with the arrow keys.
Empty Reports
| Message | Meaning |
|---|---|
| The historical database check found no errors. | The report exists but has no rows. |
| No HistDBErr.csv found in this scenario folder. | The scenario has no report. |
How to Investigate an Error
- Open the Summary viewer and look for the Historical Database errors detected warning.
- Click View Historical Database.
- Check Total Records and Remark Types.
- Use the chips to show the error type you want to investigate.
- Note the affected Unit ID, Site ID and Region ID.
- Review Max Gen, Max Cap, MR Energy and Cap Deficit together with the Remarks.
- Use Export CSV if you need to analyse the rows elsewhere.
Interpreting the Report
A row in the report is an item to investigate, not proof that the simulation is invalid. Read the unit, site and region together with the recorded values and remark — for a capacity-related remark, for example, compare Max Gen, Max Cap and Cap Deficit — and check them against the historical data and the scenario setup.
Quick Reference
| Item | Description |
|---|---|
| Where | Summary viewer → Historical & Database sub-tab |
| Source | The scenario's Historical Database error report |
| Display | One table per error type |
| Chart | None |
| Filtering | Error-type chips; All / None |
| Export | Export CSV per error type |
| Entry points | Summary sub-tab, Summary warning, Scenarios tree right-click menu |