Analyses 03 and 04 now place each day's point and bar at 12:00 UTC
instead of 23:00, where they read as the next day. Computations are
unchanged. D-019 records the choice and the rejected one-day shift of
the night-end voltage (tried in 03, then in 04 only); sheet 04 gains
limit 6 (night end of J reflects J-1), and the data-pitfalls note
explains why.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The night end and rise were anchored on the first daily maximum,
which can be the 00:00 tail of the previous evening: 2026-05-05 was
read NO_CHARGE despite a +0.079 V rise, 2026-09-30 showed a wrong
night end, and 2026-09-26 stayed unknown from 04:00 to 11:00 when
evaluated mid-day. The rise now starts from an earlier minimum and
the knee is tested on the daily minimum (min_v). VERMONT: 139 / 31 /
14 / 0.
Docs: sheet 02 page order, battery_state.py in the CLAUDE.md map,
phase C exception to "anomaly = None means UNKNOWN".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
src/analyse_03.py launches the common page; sheet 03 moves to
"prototype en place" with VERMONT results; CLAUDE.md, README and
sheet 01 list the third panel.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/analyses/analyse_03.md: design of the daily battery state
analysis (phase C, state only): FULL_CHARGE / BELOW_PLATEAU /
NO_CHARGE / PARTIAL_CHARGE per UTC day, hardware thresholds
(14.0 V end of charge, 12.8 V LiFePO4 knee), status "en conception".
- D-018: next analyses give a day-by-day state with hardware
thresholds, usable from installation day; phase C then phase B.
- docs/domaine: voltage report per battery state (charging, full,
discharging) with sources; Power dispersion on VERMONT.
- CLAUDE.md: analyses table, state and next step, domain map.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>