Commit Graph
85 Commits
Author SHA1 Message Date
maximeandClaude Opus 5.5 ae5bfdc688 Map field events to the morning journal categories (D-074)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 09:17:00 +01:00
maximeandClaude Opus 5.5 b30b781b3b Lecture : la pose de la caméra se lit avant les capteurs (D-073)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 18:30:03 +01:00
maximeandClaude Opus 5.5 55519e53b3 Loop: --ameliorer runs an improver after the releveur (D-071)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 17:11:31 +01:00
maximeandClaude Opus 5.5 a614010292 Loop: commit sessions directly on master (D-070)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 17:05:28 +01:00
maximeandClaude Opus 5.5 5ff342a7f2 Keep each case's labeling record in its own folder
- etiquetage.md sits next to etiquettes.json in every case: C-001..C-005
  moved from vues-deplacements/benchmark/etiquetage/, C-006..C-008 written
  from lot 01 (source and table of moments, coded names)
- anonymiser.py --etiquettes now writes etiquetage.md too (with its test);
  builder, /nouveau-cas, anonymiser-cas, agent spec and D-069 follow
- vues-deplacements/benchmark/ keeps only the history

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 16:54:37 +01:00
maximeandClaude Opus 5.5 d5bae7a696 Add the loop's end-of-session page and a detector benchmark on the case base
- End-of-session page for /boucle: the session's curves, the analyst's
  labels against the detectors' events per category, a plain score table
  and the benchmark (comparaison.py, D-066)
- Detectors moved to vues-deplacements/detectors/ (D-067)
- Detectors must detect everything; what the client sees is a separate
  layer (D-068)
- Benchmark: each case keeps its labels from creation (etiquettes.json),
  benchmark.py scores the detectors on every case, history in
  vues-deplacements/benchmark/historique.csv; run by /boucle at each lot,
  after each change and at the end, read by the upgrader and validator;
  labels for C-001..C-005 from one analyst pass corrected by their files,
  C-006..C-008 from lot 01 (D-069)
- Fixes from the releveur's notes: /boucle arguments and other sessions,
  branch name in the spec, detector name in categories.py output, learned
  case header, anonymiser.py (camera/, no empty CSVs, --etiquettes),
  ensemble.py (clock-aligned steps, title), plages.py (same-sign merge),
  labeling request written into /nouveau-cas
- Also carries the other session's uncommitted D-065 edits in the same
  files; data/, .gitignore, pomper.py and stations.py are left out

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 16:48:13 +01:00
maximeandClaude Opus 5.5 6b3d058a67 Pompage : métriques système dans metrics/, images absentes de S3 sautées
pomper.py écrit les métriques dans data/<SERIE>/metrics/ ; load_stations les y lit
aussi. Les images dont measurement_uuid est vide (jamais arrivées sur S3) sont
écartées de la requête : plus d'erreur de l'appli, la tranche prend l'image suivante.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 16:47:47 +01:00
maximeandClaude Opus 5.5 0c8c90d1d5 Note what DIFF and IRON camera images are, keep --diff optional (point 28)
The station manual says the DIFF image is the contrast-enhanced view of the
reflectors that the displacement algorithm measures, not a difference between
two instants. The reading tools only look at IRON images, so run.md describes
--diff as an option instead of putting it in the pump command.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 12:27:20 +01:00
maximeandClaude Opus 5.5 0372a20da9 Plan the NORDEND September sessions: /aiguiser before /boucle (points 31, 42)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 12:08:58 +01:00
maximeandClaude Opus 5.5 3ec6261b5a Pump the camera movements and add run.md with the generic pump command (point 43)
Camera pan, tilt, scale, rotation and sigma0, one row per camera measurement,
read like the platform viewer (cam_movements aggregate), one CSV per day in
camera/. Tried on NORDEND 30/07: 70 poses out of 95 instants, sigma0 on the
same 7 as the advanced export. run.md holds the command to copy into the
app's dev container.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 11:27:06 +01:00
maximeandClaude Opus 5.5 2d2d50a8b3 Run the first pump on NORDEND: identical to the received exports (point 27)
Two days (29-30/07) pumped by the user in the app's dev container: system
metrics, displacements and camera images match the received exports, and
the journal gives the same events. The container mounts ~ on /workspaces,
so the script now writes straight into Support-Agent's data/ (no copies).
Add --delai for days that exceed the 60 s query timeout, and report the
root database error instead of pandas' wrapper.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 11:13:57 +01:00
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