You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should we grab some of (or all of) these updates? (IIUC, we currently grab the initial estimate in realtime, and then we grab the updated estimate at 1100 UTC)
To keep things relatively simple, I think my suggestion would be something like this:
As per the new PV_Live README, update our "in-day" estimates every 5 minutes for the first 3 hours after the initial estimate. But keep every one of these "in-day" updates (identified in our DB using PV_Live's new updated_gmt field) so we have the option to train our ML models (in the future) on these different "in-day" estimates
Ignore the 23:00 UTC update. It's tiny.
Grab the big update at 11:00 UTC (which Peter implemented already, last night!)
PV Live national updates many times:
It updates multiple times within the first 3 hrs of the initial estimate. And those updates can be quite significant.
It updates at 2300 and 1100 UTC.
It sometimes updates a few days after the initial estimate.
(See this plot for details of when PV_Live is updated).
Should we grab some of (or all of) these updates? (IIUC, we currently grab the initial estimate in realtime, and then we grab the updated estimate at 1100 UTC)
To keep things relatively simple, I think my suggestion would be something like this:
updated_gmt
field) so we have the option to train our ML models (in the future) on these different "in-day" estimatesRelated
The text was updated successfully, but these errors were encountered: