Commit Graph
6 Commits
Author SHA1 Message Date
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 9be9a636f7 Shade battery state voltage zones on the BusVoltage plot
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>
2026-10-12 10:45:43 +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
maximeandClaude Opus 5.5 7b1da6d7cf Add analysis 02 (midnight sample), simplify plots, spell out rule names
- 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>
2026-10-12 09:31:52 +02:00
maximeandClaude Opus 5.5 8992bda17e Document the project: decisions log, analysis sheet, domain notes
- 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>
2026-10-09 23:29:42 +02:00