-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First day after calculation (UTC or Europe/London) #22
Comments
Hi @peterdudfield, |
I've been pulling PV_Live data every 15 minutes since Tuesday evening (and saving every "pull" separately). Below is a plot of the changes in the data: All subplots share the same x-axis. The x-axis is the datetime (UTC) that I polled the PV_Live API. In the top subplot ("Changes to PV_Live National estimate"):
The three lower subplots show how the PV_Live national estimate for 9:00, 12:00, and 18:00 change over subsequent pulls. If I've understood correctly, some conclusions are:
Does that sound about right? |
@JackKelly That's exactly what I would expect to see based on our scheduling and matches our recommended polling cycle (now included in the README) Great plots - excellent way to visualise the impact of retrospective revision. It'd be interested to see something similar aggregated over more days, correcting for capacity and considering seasonality. I know I still have a similarly-themed email from you to follow up on - hoping to get to this next week! |
Picking up from email thread about simulating historical PV_Live outturns using only the intraday/near-real-time sample... I've uploaded some historical simulated intraday PV_Live outturn estimates here: And done some brief sense-checking/analysis here: Preliminary conclusions:
|
Awesome, thank you so much @JamieTaylor-TUOS! |
Just want to check following on from #20 that the first day after calculation is made roughly at 10.30 UTC not Europe/London time? For some reason i thought it was local time
Small code to show its UTC
The text was updated successfully, but these errors were encountered: