Commit Graph
10 Commits
Author SHA1 Message Date
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 3082f75429 Add analysis 04 entry point and documentation
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>
2026-10-12 11:36:26 +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
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
maximeandClaude Opus 5.5 57ea286014 Fill CLAUDE.md with project context
Project goal, decisions taken so far (energy health first, analytics
only, embedded target, no synthetic data), annotated data cases,
domain essentials from doc/ and non-negotiable diagnostic rules.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 17:05:11 +02:00
maximeandClaude Opus 5.5 f1f28535bd Add hooks/agents/skills folders and CLAUDE.md header
Empty hooks section in settings.json, .gitkeep'd folders for hook
scripts, subagents and skills.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 15:59:53 +02:00
maximeandClaude Opus 5.5 a9dfba930d Add empty Claude Code harness
CLAUDE.md skeleton, project settings (deny .env reads), .gitignore.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 15:58:22 +02:00