Commit Graph
24 Commits
Author SHA1 Message Date
maximeandClaude Opus 5.5 7714a55cfa Score the detectors against every label of the station at each loop batch (D-062, point 45)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 11:25:12 +01:00
maximeandClaude Opus 5.5 02ed7a4a60 Record the analyst's labels at every loop batch (D-061, point 44)
Each batch now leaves etiquettes.json next to the critique: the analyst's
own reading, written before the detectors' output, one entry per moment,
checked by critiquer-lot/etiquettes.py against the event map and the
station's sensors. Groundwork for a future learned model.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 09:39:34 +01:00
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 6ed1264ec8 Add point 43 to the living plan: a complete, incremental local database
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 16:35:30 +02:00
maximeandClaude Opus 5.5 e5c03b1d4a Record the reading sharpening decision (D-059)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 16:33:19 +02:00
maximeandClaude Opus 5.5 54d1c6a142 Document the automatic loop as validated, run lot by lot by the user (D-057)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 15:26:36 +02:00
maximeandClaude Opus 5.5 6be683819e Record the automatic loop decision (D-057)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 15:14:14 +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 86547f089b Grade visibility, add the periodic effect and the slow drift to the morning journal (D-056)
- Visibility: v0 kept after a measured trial of a simpler version (archived); two levels, Reduced and No visibility
- Thermal: a 24-hour sinusoid confirms the daily wave, split into thermal expansion and contraction events
- Jumps tested from the first measurement; turbulence never kept over a shift to check (CLARIDEN)
- Data gaps say whether camera images exist; Displacements trends become slow drift events
- Threshold registry moved to vues-deplacements/contexte/seuils-du-journal.md; plan points 11 to 17, 38 and 41 validated

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 12:22:06 +02:00
maximeandClaude Opus 5.5 4ac95ae1ca Classify the morning journal into eight categories and validate plan points 1 to 10 (D-056)
- Event map regrouped into six families, 33 events including hypothetical ones, with the journal categories (section 4)
- categories.py turns detector episodes into categorised events: absorption of brief jumps, merging, catégorique phrases
- Journal tab: one "What happened" row coloured by family, cards, and an Images button playing the event's timelapse
- Plan: user-validated points marked, points 39 and 40 added; anomaly definition clarified in D-056

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 11:02:38 +02:00
maxime ebcdb30375 doc planning 2026-10-24 08:24:30 +02:00
maxime 23f01d7c23 nouvelle planification 2026-10-23 21:52:08 +02:00
maximeandClaude Opus 5.5 6587a08723 Add the implementation plan of the Explore mockup; color the grid by deviation from the first 24 h (D-053)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 14:50:27 +02:00
maximeandClaude Opus 5.5 ee61d62d79 Document the diagnostic agent case base: spec, D-048, README and CLAUDE.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 16:34:45 +02:00
maximeandClaude Opus 5.5 7892fd9126 Plan the diagnostic agent implementation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 14:55:28 +02:00
maximeandClaude Opus 5.5 c97bd71b95 Plan the Storage and Cellular domains and the nouveau-domaine skill
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 09:36:26 +02:00
maximeandClaude Opus 5.5 2e0f9cfa1c Do not restrict the WEISSHORN working set to its first export dates
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 09:31:54 +02:00
maximeandClaude Opus 5.5 ed0a5ae790 Add WEISSHORN as the working set of the Storage and Cellular domains
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 09:26:44 +02:00
maximeandClaude Opus 5.5 ac2e95a90a Spec the Storage and Cellular domains and the new-domain procedure
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 09:22:32 +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 722ea0841b Plan analysis 04 DAILY_BATTERY_TREND implementation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 11:31:32 +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 55ec0499bb Add implementation plan for MA7D_DROP energy analysis
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>
2026-10-09 18:38:50 +02:00
maximeandClaude Opus 5.5 e07656902a Add design spec for MA7D_DROP energy analysis
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>
2026-10-09 18:31:38 +02:00