src/analyse_04.py launches the common page; sheet 04 moves to
"prototype en place" with VERMONT results; CLAUDE.md, the analyses
rule, README and sheet 01 list the fourth panel and extend the
"no verdict" contract exception to analysis 04.
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>
One state per UTC day from BusVoltage: FULL_CHARGE, BELOW_PLATEAU,
NO_CHARGE, PARTIAL_CHARGE or unknown, with hardware thresholds
(14.0 V end of charge, 12.8 V LiFePO4 knee). No verdict yet.
Includes the implementation plan.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Background bands for discharge (12.0-13.2 V), charging (13.1-13.8 V)
and full charge (14.0-14.4 V), from the battery voltage report.
Display only, no effect on the analyses.
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>
- Analysis 02 MOVING_AVERAGE_7_DAYS_MIDNIGHT_UTC_DROP: same rule as
analysis 01 on the 00:00 UTC BusVoltage sample only, one point per
day. Shared computation in energy_check._ma_drop(); analysis 01
results unchanged on VERMONT.
- Common page: one panel per analysis (02 under 01), then the time
series (D-016); src/analyse_02.py launches that page.
- Analysis panel reduced to two curves on one volt axis: 7-day mean
and threshold; gap and reference moved to hover (D-015).
- Date tick labels under every subplot.
- Rule IDs spelled out: MA7D_DROP -> MOVING_AVERAGE_7_DAYS_DROP,
MA7D_MIDNIGHT_DROP -> MOVING_AVERAGE_7_DAYS_MIDNIGHT_UTC_DROP (D-017).
- Docs: analysis sheet 02, sheet 01, CLAUDE.md, README, decisions
D-015..D-017, analysis rule and nouvelle-analyse skill.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- CLAUDE.md becomes a short map: status and next step, analyses index,
documentation map, working rules.
- docs/decisions.md: ADR-style project decision log (D-001..D-014).
- docs/analyses/: living sheet per analysis (analyse_01) and template.
- docs/domaine/: domain knowledge, one note per question.
- .claude/rules/analyses.md: path-scoped rule loaded on src/ and
docs/analyses/; .claude/skills/nouvelle-analyse: new-analysis workflow.
- README.md: human entry point.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Four TDD tasks: CSV loading, causal analysis, periods/summary/CLI,
plotly report. Code validated against real data in a prototype.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
First analysis of the station energy-health use case: 7-day moving
average of BusVoltage compared to its own 30-day maximum, evaluated
causally at each hourly point, with a plotly visualisation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>