Commit Graph
37 Commits
Author SHA1 Message Date
maximeandClaude Opus 5.5 a81cc4c380 Pump system metrics and resume day by day (point 43)
pomper.py now also pumps every system metric of a station, in the format of
the System page download (hourly mean, text lists, empty hour), one CSV per
metric and per day; displacements are written one file per day, today is
never pumped, and a rerun only fetches missing days. Fix image resume: an
image already on disk now counts for its time slot. load_stations merges
several files of the same metric instead of failing on a duplicate.

Not run against the database: first run by the user, with point 27.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 19:14:59 +02:00
maximeandClaude Opus 5.5 955566d86f Clean the journal curves, unfold its timeline and sort it in batches (D-056)
Plan points 18 to 26, 30, 39, 40 and the point 37 housekeeping:
- greyed zones per target, vertical scale without the zones to ignore, Fit all,
  mm by default with a px switch, Support view, Expand (one row per category);
- cleaned curves: cut in the zones to ignore, raw data kept there in thin grey;
- target02 to target05 count as targets; smoothing questions answered;
- categories.py sorts in slices with 3 days of history by default;
- the pumping script points to ~/monitoring-dashboard and skips diff images;
- CLAUDE.md back under 200 lines; a case page is named after its case.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 14:31:42 +02:00
maximeandClaude Opus 5.5 997e842568 Rename DAILY_MAINS_POWER to DAILY_POWER_SOURCE
The user's preferred name. The module becomes src/energy/power_source.py
and the sheet docs/energy/analyses/daily_power_source.md; the
calculation and the results are unchanged (D-043).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 17:23:26 +02:00
maximeandClaude Opus 5.5 9177982de1 Add DAILY_MAINS_POWER: on mains, a mains loss turns the day red at once
A station is on mains when its BusVoltage mean over the 3 days before
the day is >= 14.0 V (solar never exceeds 13.50 V on VERMONT; mains
stays >= 14.08 V). On mains, the mains loss decides the day color
instead of the state x trend matrix: red as soon as an hour falls under
13.4 V (top of the OCV plateau; mains-on hours stay >= 13.65 V, mains-off
hours are 13.1-13.3 V). On MISSISSIPPI the day turns red 1-2 h after the
loss instead of 29-40 h with the matrix; WEISSHORN and NORDEND (mains)
raise no false alert, VERMONT (solar) is unchanged (D-043).

The matrix drawio gets the mains case, the site figure a third panel,
and the support notification and the client Energy block header show
"On mains" / "Not on mains" / "Mains unknown".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 17:22:16 +02:00
maximeandClaude Opus 5.5 27c52bac75 Deliver Temperature in the mockups, with its site figure and guide
Temperature joins the mockups' list of domains (D-041): a Red
notification on the support Home, and a one-line block on the client
view ("Hottest (24 h) 43 °C · limit 97.5 °C") for the stations that
measure the GPU. src/temperature/final.py writes the site figure; the
comparison page reuses its panel. Short two-layer guide in
docs/temperature/guide/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:11:21 +02:00
maximeandClaude Opus 5.5 276c34ea38 Add the temperature domain on the GPU manufacturer limit
DAILY_GPU_TEMPERATURE_LIMIT: red when an hourly GPU mean reached 97.5 °C
(T.gpu, Jetson Nano Thermal Design Guide) in the last 24 hours, green
otherwise, gray without measurement. Working sets WEISSHORN and NORDEND;
all measured days are green. D-040 replaces D-036; the exploration note
moves to docs/temperature/domaine/point-de-depart.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:07:36 +02:00
maximeandClaude Opus 5.5 f0990c16e6 Deliver Storage and Cellular in the mockups, with site figures and guides
The mockups now walk a list of domains (D-039): the support Home loads
every station in data/ and notifies each station x domain that is Orange
or Red; the client view becomes maquettes/user/summary.py, one System
Summary page per station with one block per measured domain. Storage
shows a free-space scale and the estimated full date; Cellular shows the
day's sends in words and a four-class signal scale.

HEADLINE moves into each day_color.py, with a Green sentence for the
client view. src/storage/final.py and src/cellular/final.py write the
site figures in English; the comparison pages reuse their panels. Each
domain gets a short two-layer guide in docs/<domaine>/guide/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:05:26 +02:00
maxime 5a886b4e7e cellular + storage analysis 2026-10-13 12:50:15 +02:00
maximeandClaude Opus 5.5 d43db2a66a Add the storage analyses and their day color
DAILY_STORAGE_STATE classifies the end-of-day free space of /data and
DAYS_UNTIL_STORAGE_FULL divides it by the median daily fill over 7
days. The day color reads a state x horizon matrix drawn in
docs/storage/matrice-etat-horizon.drawio. Thresholds are arbitrary for
now (D-034, D-035); expert questions stay open. On WEISSHORN the disk
fills at 28.2 MiB/day and would be full around 06/02/2027.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 12:33:11 +02:00
maximeandClaude Opus 5.5 75b681d2db Rerun the cellular analyses on the 65-day WEISSHORN export
WEISSHORN now shows its commissioning (link down on 19-20/08), a send
cadence that settles on 01/09, six days with one to three missing
sends and one DOWN day from a single down sample. Update the starting
note, both fiches and the expert questions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 12:33:10 +02:00
maximeandClaude Opus 5.5 f803a7d596 Count sends without link and add NORDEND to the cellular working set
DAILY_LINK_STATE falls back on last_sync for exports without link,
treats the start of history as unknown, and records D-032. Document
the hourly counting flaws, the observed 15-minute cadence, and the
open questions for the specialist.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 11:50:07 +02:00
maximeandClaude Opus 5.5 91ba1bd8ef Add the DAILY_LINK_STATE and DAILY_SIGNAL_STATE cellular analyses
Explore WEISSHORN for the cellular domain, count lost sends and
messages, grade the daily RSRP and RSRQ medians on the published
Quectel grid, and record D-031.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 10:48:34 +02:00
maximeandClaude Opus 5.5 f8a81c0990 Load text metrics as lists of the hour's samples
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 10:48:34 +02:00
maximeandClaude Opus 5.5 504c8634e3 Add the Storage and Cellular domains with their starting notes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 09:38:33 +02:00
maximeandClaude Opus 5.5 c3e9eef4e4 Move the VERMONT CSVs into data/VERMONT
New data will be added per station without mixing with the working set.
All scripts now default to data/VERMONT/; docs and D-029 follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 09:10:35 +02:00
maximeandClaude Opus 5.5 7f911e41a3 Rename the delivered Energy script daily.py to final.py
src/energy/final.py is daily.py unchanged; the comparison script, the
day focus and the client mockup now import energy.final. References in
the README, the analysis rule, the nouvelle-analyse skill, the two
delivered analysis sheets and the guide follow. Output files keep
their names (out/<STATION>_daily.html and .json).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 08:58:43 +02:00
maximeandClaude Opus 5.5 8a32f4d418 Organize the project by domain and name analyses by their rule
Energy code moves to src/energy/ and its docs to docs/energy/; shared code
(CSV loading, venv switch, browser, zoom script) goes to src/common/, and the
AIMsight originals to docs/aimsight/. Analyses are no longer numbered: two
Energy scripts remain, daily.py (delivered state and trend) and
all_analyses.py (comparison of the four). Calculations and pages unchanged (D-026).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 17:12:37 +02:00
maximeandClaude Opus 5.5 1a2220d317 Add the day focus: a day and the day before only
D-024: to explain a day's color, show only that day and the day before,
the only days analyses 03 and 04 read for it. day_color.focus() selects
the data (standard library); src/focus_jour.py prints a traceable fact
summary and writes a 48 h BusVoltage figure (out/<STATION>_focus_<date>
.html and .json). Analysis 03 gains the night_end_h fact; the other
facts are unchanged. The client Energy mockup does not use this figure:
the user prefers numeric facts there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 16:23:45 +02:00
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 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 e058a2e3e7 Plot DAILY_BATTERY_TREND as the fourth analysis panel
One bar per day for the night-end voltage delta, coloured by trend
(blue better, grey stable, red worse), with the 0.05 V dead band.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 11:35:40 +02:00
maximeandClaude Opus 5.5 005e006b2f Add analysis 04 DAILY_BATTERY_TREND computation
Day-over-day trend from DAILY_BATTERY_STATE: a state change decides
(FULL > PARTIAL > NO_CHARGE > BELOW_PLATEAU), otherwise the night-end
voltage delta with a 0.05 V dead band. No verdict (anomaly = None).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 11:34:00 +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 a3590fab62 Plot DAILY_BATTERY_STATE as the third analysis panel
Daily maximum and night-end voltage, 14.0 V and 12.8 V thresholds,
one marker colour and symbol per day state.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 10:52:40 +02:00
maximeandClaude Opus 5.5 1ae176cc5a Add analysis 03 DAILY_BATTERY_STATE computation (phase C)
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>
2026-10-12 10:52:08 +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 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 0b950199b8 Rework analysis 01 entry point and plots, drop tests
- src/analyse_01.py: single entry point, analyses data/, writes and
  opens the HTML report (switches to .venv for plotly).
- Plot: analysis on top, one subplot per time series below; zoom in
  time only, y axes rescaled to the visible range on every zoom.
- Tests removed: experimental prototype phase (D-008).
- Ignore __pycache__/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 23:29:42 +02:00
maximeandClaude Opus 5.5 128d4bc298 Add AIMsight docs, Vermont working data and collector reference
- doc/: AIMsight reference documentation and station manual.
- data/: VERMONT complete dataset (7 system metrics) and expert
  diagnostics; other incomplete stations set aside in data/archive/.
- src/__main__ (3).py: reference copy of the embedded system_info
  collector (INA219 units, LiFePO4 OCV table).
- architecture.drawio: user-maintained architecture diagram.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 23:29:42 +02:00
maximeandClaude Opus 5.5 53b4f7e47c Harden MA7D_DROP inputs and report UNKNOWN stretches
- NaN/inf values are treated as missing instead of poisoning the
  running sum (which produced a false "not observed").
- Unreadable CSV files are skipped with a message naming the file;
  a station whose analysis fails is skipped with its name and the
  scan continues.
- The summary now states hours without verdict and the longest
  UNKNOWN stretch (5 months on MISSISSIPPI were silent).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 19:37:56 +02:00
maximeandClaude Opus 5.5 79bd98c9cb Add plotly HTML report for MA7D_DROP
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 19:27:28 +02:00
maximeandClaude Opus 5.5 d91ab866e2 Add anomaly periods, text summary and CLI for MA7D_DROP
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 19:26:44 +02:00
maximeandClaude Opus 5.5 041770ec47 Add causal MA7D_DROP voltage-trend analysis
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 19:26:00 +02:00
maximeandClaude Opus 5.5 422904757f Add CSV loading per station for energy analysis
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 19:25:26 +02:00