From 05c8d81c8c6e67cedc1db86f9cb51fefa62d79fb Mon Sep 17 00:00:00 2001 From: Jamie Taylor Date: Tue, 28 Apr 2026 11:33:27 +0100 Subject: [PATCH 1/2] Update README.md Update timings for the day+1 revision in the README to accurately reflect latest job schedules --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f10fbcc..79a3857 100644 --- a/README.md +++ b/README.md @@ -203,7 +203,7 @@ Since the PV_Live model produces outturn estimates, they will never strictly spe - Outturns are re-computed in near-real-time every 5 minutes after the end of the half-hour for 3 hours, to allow for late arriving sample data - If all data ingestion pipelines are running smoothly, this does not result in any retrospective revisions - If some near-real-time sample data is late arriving, the outturn estimate will be revised at the next update -- Outturns are re-computed on day+1 (typically between 10:30 and 10:35 and again between 22:30 and 22:35) to make use of sample data which only becomes available on day+1 +- Outturns are re-computed on day+1 (typically between 10:42 and 11:00 UTC and again between 22:42 and 23:00 UTC) to make use of sample data which only becomes available on day+1 - Historical outturns may be re-computed periodically whenever our PV deployment dataset is updated retrospectively (usually every 3 - 6 months) In order to maintain a local copy of the PV_Live GB national outturn estimates that is as in sync with our own latest/best estimates as possible, we recommend the following polling cycle: From 1aada508a576ae5f2760edce85490a0636bebd89 Mon Sep 17 00:00:00 2001 From: Jamie Taylor Date: Mon, 11 May 2026 13:29:42 +0100 Subject: [PATCH 2/2] Apply suggestion from @JamieTaylor-TUOS Updated to reflect the fact that 22:42 run was removed --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 79a3857..1a47e62 100644 --- a/README.md +++ b/README.md @@ -203,7 +203,7 @@ Since the PV_Live model produces outturn estimates, they will never strictly spe - Outturns are re-computed in near-real-time every 5 minutes after the end of the half-hour for 3 hours, to allow for late arriving sample data - If all data ingestion pipelines are running smoothly, this does not result in any retrospective revisions - If some near-real-time sample data is late arriving, the outturn estimate will be revised at the next update -- Outturns are re-computed on day+1 (typically between 10:42 and 11:00 UTC and again between 22:42 and 23:00 UTC) to make use of sample data which only becomes available on day+1 +- Outturns are re-computed on day+1 (typically between 10:42 and 11:00 UTC to make use of sample data which only becomes available on day+1 - Historical outturns may be re-computed periodically whenever our PV deployment dataset is updated retrospectively (usually every 3 - 6 months) In order to maintain a local copy of the PV_Live GB national outturn estimates that is as in sync with our own latest/best estimates as possible, we recommend the following polling cycle: