Commit Graph
6 Commits
Author SHA1 Message Date
maximeandClaude Opus 5.5 8452973912 Add the client Energy mockup and switch site texts to English
D-022: page mockups are HTML built from real data, in maquettes/user/
(client) and maquettes/support/; Figma only on request.
maquettes/user/energy.py renders the System Summary page with a
Diagnostic section: an Energy box with the day's color, a one-line
headline, a battery scale (zones from the collector's LiFePO4 OCV
table, no percentage shown), the trend against the day before, an
"Activate energy save mode" button on orange and red days (mockup
only, sends nothing), and two collapsibles: the full history (D-021
figure) and the guide (part 1 of the manual, rendered from Markdown).

D-023: everything meant for the monitoring site is in English,
including the titles, legends, axes and hovers of the 03/04 panels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 16:23:37 +02:00
maximeandClaude Opus 5.5 fc74fec10f Add the day color matrix, the energy diagnostic manual and the site figure
D-020: the delivered energy diagnostic keeps analyses 03 and 04 only,
combined by the state x trend matrix of cas-d-usage-03-04.drawio into
one color per day (green / orange / red, grey when unknown), coded in
src/day_color.py (standard library). docs/guide/diagnostic-energetique.md
explains it: part 1 for the client, part 2 for support.

D-021: energy_plot.daily_figure builds the figure for the monitoring
site (panel 03 above panel 04, shared time axis), written by
analyse_01.py as out/<STATION>_daily.html and .json. battery_state no
longer imports energy_check, so analyses 03 and 04 ship on their own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 16:23:21 +02:00
maximeandClaude Opus 5.5 129d4ff59b Plot daily analysis points at noon of their day
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>
2026-10-12 12:11:45 +02:00
maximeandClaude Opus 5.5 5e039ef3bb Fix DAILY_BATTERY_STATE night end and rise, document phase C contract
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>
2026-10-12 11:03:23 +02:00
maximeandClaude Opus 5.5 eacc0ecd4a Add analysis 03 entry point and documentation
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>
2026-10-12 10:53:15 +02:00
maximeandClaude Opus 5.5 e77d3e4b82 Spec analysis 03 DAILY_BATTERY_STATE, battery voltage report
- 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>
2026-10-12 10:43:36 +02:00