Earth Notes: On Website Technicals (2024-09)
Updated 2024-09-11.2024-09-11: Adjusting Ps and Qs
I have adjusted P/p and Q/q to for a threshold CoP of 2, as that is the case now and shows that it can happen!
2024-09-05: Minding Ps and Qs
I have adjusted P/p to use CoP% (ie if current intensity is a little under predicted then the value is a little over 100), and over 150 now flags significant saving from topping-up storage.
This numeric value allows a smooth fading in of maximum top-up percentage from (say) a CoP% of 150 to 250, eg with a mean of 200%.
Right now I am seeing both P
and Q
flags, but no 'supergreen' G
(though grid is ordinary green).
2024-09-05T14:26Z MT 41 GI 78 IT 169 F PQbvx ES 1
A matching change has been made for calculating Q
/q
and a CoP >150% significance threshold.
The grid went supergreen at 4pm ie peak time (H
), so a top-up would have been locked out here:
2024-09-05T14:31Z MT 41 GI 78 IT 168 F PQbvx ES 1 2024-09-05T14:36Z MT 41 GI 78 IT 168 F PQbvx ES 1 2024-09-05T14:41Z MT 1 GI 78 IT 0 F PQbvx ES 1 2024-09-05T14:46Z MT 1 GI 78 IT 0 F PQbvx ES 1 2024-09-05T14:51Z MT 1 GI 80 IT 0 F PQbvx ES 1 2024-09-05T14:56Z MT 1 GI 82 IT 0 F PQbvx ES 1 2024-09-05T15:01Z MT 0 GI 86 IT 0 F HGPQbvx ES 1 2024-09-05T15:06Z MT 0 GI 85 IT 0 F HGPQbvx ES 1
(Intensity has sharply fallen over 24h and is due to rise again over 48h...)
Moments that are supergreen (G
) and with at least one of P
and Q
can be picked out with something like:
% egrep ' F [^ ]*[PQ]' data/heatBattery/log/live/20240905.log | egrep ' F [^ ]*G'
2024-09-04: Q/q Flag
I added a Q
(and converse q
) flag (indicating that a big grid intensity fall has happened over the last 7d, so storing heat now would have an effective CoP >1) to script/heat-battery-target.sh
output to estimate how often it might drive a top-up, with an initial threshold value of a CoP >2.0.
Yes, all the good and obvious flag letters have been used...
2024-09-03: P/p Flag and GSC 304s
I added a P
(and converse p
) flag (indicating that a big grid intensity rise is predicted over the next 48h, so storing heat now would have an effective CoP >1) to script/heat-battery-target.sh
output to estimate how often it might drive a top-up eg 2024-09-03T14:31Z MT 0 GI 225 IT 139 F Rpbvx ES 3
, with an initial threshold value of a CoP >2.0.
304s
Google Search Console now reports that 29% of recent crawls of EOU by Google get 304s now. A number that has been rising steadily, mainly because I stopped using ETag
s I suspect.
2024-09-02: Zero Gas Ahoy
Anticipting the heat pump getting installed, and thus gas consumption dropping to zero, I adjusted the recent utilities consumption working from the form At 16WW over 32 days from 2024-08-01 to 2024-09-02: gas consumption was 0.2kWh/d, electricity imports were 0.4kWh/d (net -9.5kWh/d).
to At 16WW over 32 days from 2024-08-01 to 2024-09-02: electricity imports 0.4kWh/d (net -9.5kWh/d), gas consumption 0.2kWh/d
, with the gas clause disappearing entirely when zero.