Commit Graph
106 Commits
Author SHA1 Message Date
maximeandClaude Opus 5.5 0544956c87 Status page: details and timelapse of the selected status below the plots
A click on a status label shows, below the figure, its details (name, times, sensors, sentence,
then References and Targets per sensor) and, on the right, the timelapse of its camera images,
as in detecteurs.py. Clicks in the details keep the selection; a click elsewhere clears them.

detecteurs.py shares its pieces instead of status.py copying them: the timelapse JavaScript
(TIMELAPSE_JS, the image slider stays in IMAGES_JS), the player HTML and CSS, camera() for the
images and sensor positions, and groupes() with French or English texts. The player's few
messages are now in English (before / DURING / after, no image, GIF export error).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 12:14:18 +01:00
maximeandClaude Opus 5.5 5b16354776 Status page: clicking a status no longer zooms
The click keeps only the status's sensors and highlights its bands; the time range, including a
zoom made by hand, stays as it is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 11:49:57 +01:00
maximeandClaude Opus 5.5 d62017e060 Status page: thermal merge suspended, expansion and contraction shown separately again
Merging the two thermal phases into Thermal movements only holds for phases on the same targets;
the user has not decided yet. hierarchie-des-status.md keeps the merge; status.py, CLAUDE.md and
D-095 say it is suspended. Occultation and the target filter are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 11:47:11 +01:00
maximeandClaude Opus 5.5 dcbffeaa71 Status page: status hierarchy and filter by visible targets (D-095)
detectors-view/hierarchie-des-status.md, validated by the user: No visibility hides Reduced
visibility, Faulty target hides Target hidden, No data hides everything, No visibility hides Target
hidden; the two thermal phases form one status, Thermal movements. A hidden status is cut, not
removed, and only when the stronger one covers all its sensors. status.py transcribes it.

Hiding or isolating targets in the sensor legend keeps only the statuses that touch a visible
target, or all sensors. Discarded labels become transparent, without text, hover or click:
restyling x or base of the label row made Plotly retype its axis as linear.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 11:42:18 +01:00
maximeandClaude Opus 5.5 71111b9f29 Status page: clickable event labels above the curves select an event
One label per detector event at its time, in its category colour, overlapping events on lower rows.
A click zooms on the event (half its duration on each side, 1 h to 6 h), keeps only its sensors and
highlights its band; a second click shows everything again. The range is set on every x axis: in
the same relayout as the band opacities, the axes matching the bottom one did not follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 11:17:15 +01:00
maximeandClaude Opus 5.5 88b9551d9d Status page: corr_x, corr_y, camera movement and detector events as colored bands (D-094)
detectors-view/status.py, a pseudo-final version of the site's Explore page: the curves with the
legend on the right, each detector event as a transparent band over them (one colour per category,
legend above), without Shift to check and Slow drift as in the Status line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 11:10:29 +01:00
maximeandClaude Opus 5.5 e3150cf96c Reading tools: quality/ files are no longer read as displacement exports; run-detectors.sh runs the detectors page on every station
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 10:42:21 +01:00
maximeandClaude Opus 5.5 10e122067a Detectors page moves to detectors-view/ with its display helpers (D-093)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 10:37:37 +01:00
maximeandClaude Opus 5.5 3d989b93ef CLAUDE.md: state at 2026-10-29, events-learner roles, skill list and sizes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 10:31:53 +01:00
maximeandClaude Opus 5.5 3b732adc52 Loop renamed events-learner; end benchmark on the same events; spec reduced to the why (D-092)
- /boucle becomes /events-learner: skill and scripts in
  .claude/skills/events-learner/, sessions in events-learner/, spec
  vues-deplacements/contexte/events-learner.md, end page
  out/events-learner_<session>.html, commits "Learn <STATION> ...";
  history keeps /boucle, the review page reads both.
- No benchmark-fin.txt: the end benchmark is the last kept
  modification's, on the same events as the start.
- The spec keeps only the why; the how lives in the skill and agents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 10:27:05 +01:00
maximeandClaude Opus 5.5 79d83be3ff Loop: the builder becomes the event-builder, called every batch (D-091)
- event-builder: called at every batch, reads the whole analysis and
  decides on its own, against the event base, what is new; an event
  keeps the bounds of the event, not of the batch (plus 6 h).
- the "Nouveautés" section leaves the analysis and the upgrader's
  output; the summary lists contradictions with the base.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 10:17:54 +01:00
maximeandClaude Opus 5.5 c763cda5c3 Loop: the analyst analyses, a new detectors-critic critiques (D-090)
- analyste: the most precise analysis of the batch, detectors allowed as
  a tool; reading, labels, known events, novelties in analyse.md; skill
  critiquer-lot renamed analyser-lot.
- detectors-critic: compares the detectors to the analysis event by
  event, without looking at the data; verdict and at most two
  suggestions in critique.md, read by the detectors-upgrader.
- /boucle step 2, builder, review page, /new-event and score.py import
  follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 09:58:48 +01:00
maximeandClaude Opus 5.5 21f8cd1db6 Loop: upgrader and validator become detectors-upgrader and detectors-control (D-089)
- detectors-upgrader: makes the detectors better on the batch from the
  analyst's critique; adds, removes or modifies, removing first; targets
  the significant events missed or badly bounded, not a perfect match.
- detectors-control: the guard against overfitting; never looks at the
  batch, judges the diff and the benchmark on the event base, decides,
  and sends its remarks back to the upgrader.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 08:45:57 +01:00
maximeandClaude Opus 5.5 ba2e9da3ab Analyst: consults the event base whenever it wants (D-088)
The event base is the analyst's knowledge base, read before or during
its reading; a known event is a lead to check on the data, not a
conclusion. No measurement of the analyst's progress.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 08:02:25 +01:00
maximeandClaude Opus 5.5 c481323dc5 Event map: learns from each validated event, shown with the fiche (D-087)
- Catch-up: E-004, E-006, E-007, E-008, E-010, E-011 in the map; new
  section 5 "Faux amis"; rejected E-009 no longer cited.
- /review-event and /new-event: what the event teaches goes into the
  map at validation, shown to the expert with the fiche.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 07:44:26 +01:00
maximeandClaude Opus 5.5 446fde3192 Events: read-event skill to consult the base (D-085), cases renamed events E-xxx (D-086)
- read-event: map and index first, then the card of close events only,
  then their data with the reading tools; never all cards at once.
  Diagnostic agent, critiquer-lot and builder point to it; the index
  header too. Signature length: about 250 characters, a guideline.
- "Cas" becomes "event": events/E-xxx/event.md, skills new-event,
  review-event, anonymize-event.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 07:25:29 +01:00
maximeandClaude Opus 5.5 4d99585474 Detectors, loop and sharpening sessions moved to the repo root (D-084)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 17:19:51 +01:00
maximeandClaude Opus 5.5 cbdf91068b Docs: handoff moved to docs/aimsight/, CLAUDE.md and README.md rewritten (D-083)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 16:54:37 +01:00
maximeandClaude Opus 5.5 0df340231a Diagnostic agent: agents/diagnostic/ renamed agent-diagnostic/ (D-082)
The diagnostic agent is kept in case it is needed again, under a name that
says what it is; entry point still .claude/agents/diagnostic.md; paths updated
in skills, agents, spec, contexts, the living plan and CLAUDE.md; reports and
history keep old paths. Also: two stale tool paths in the living plan.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 16:45:02 +01:00
maximeandClaude Opus 5.5 56b93e9b82 Agent tools: reading tools moved to agent-tools/ (D-081)
The reading tools leave agents/diagnostic/outils/ for a root folder of their
own; paths updated in skills, agents, detectors, scripts, case fiches,
support/, contexts and CLAUDE.md; graphique, vignettes and gif find the repo
root one level up; history keeps old paths.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 16:36:45 +01:00
maximeandClaude Opus 5.5 cb98818712 Events: cases, event map and eventualities graph moved to events/ (D-080)
The case base leaves agents/diagnostic/cas/ for a root folder of its own,
with the event map and its graph; paths updated in skills, agents, scripts,
case fiches, contexts, the living plan and CLAUDE.md; history keeps old paths.
Also: plan point 51, an analyst that improves from session to session.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 16:32:06 +01:00
maximeandClaude Opus 5.5 02f2bf5369 Support-agent: /support skill answers a client's question, GIF tool, first case LENZSPITZE (draft)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 11:12:28 +01:00
maxime b7f489b539 changes 2026-10-27 10:32:46 +01:00
maximeandClaude Opus 5.5 2d89c21df1 Add --ameliorer to /aiguiser, like /boucle (D-076)
The same ameliorateur agent runs after the releveur; its scope now depends
on the process named in its request.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 09:46:11 +01:00
maximeandClaude Opus 5.5 d2a1fcef25 Ajouter le détecteur degradee et la ligne Error rate de la page des détecteurs
Détecteur degradee : une cible rejetée la plupart du temps, jour après jour,
quand les autres sont vues (catégorie cible_degradee, grisée, comptée par la
boucle). Page detecteurs.py : error_value moyenne de tous les capteurs à chaque
instant, du vert au rouge, sous les barres.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 09:00:34 +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 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 Sonnet 5.5 b3c77c5caf Add Handoff.md (site health and client notifications, G) and list its gaps with the project
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-26 12:49:08 +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 add165dc38 Let every agent inherit the session model and effort (D-063)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 12:09:12 +01:00
maximeandClaude Opus 5.5 b1d2e2f531 Add the generic /aiguiser command to run.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 12:09:07 +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 da34d16d06 Add draw.io diagrams of the AI pipelines: overview, /boucle, /aiguiser, diagnostic agent
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 19:20:25 +02: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 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 260d7f70fc Add the releveur agent for difficulties in automatic processes (D-060)
Each /boucle subagent now ends its output with a Difficultés section;
at the end of a session the orchestrator calls the releveur once, which
locates the instruction or file at fault and records it in
docs/ameliorations-processus.md, without fixing anything.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 16:22:30 +02:00
maximeandClaude Opus 5.5 4d14f5ea5d Open the diagnostic agent to project knowledge and the journal detectors (D-058)
The agent now serves one precise case, reads the project's displacement
knowledge and the whole case base, starts from the detectors' events
without judging them, and no longer has conclusions imposed on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 15:46:30 +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 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 8d9b927600 Show each jump and trend on the curves when hovering its row (D-055)
The Displacements tab now puts the list on the left and the curves on
the right, kept on screen while the list scrolls. Hovering a row keeps
only its target in color and draws it on the curves, with fixed scales:
a jump gets its 2 hours highlighted, the 24 h levels before and after
and an arrow with the jump in mm; a trend gets its period, the
Theil-Sen line, the daily levels, its start and end and the drift as
an arrow. #focus=j0-0, t0 or e0 opens with a row hovered, for captures.

Documented in the detection note: on NORDEND, PR17 and PR06 clear the
thresholds by a wide margin, the next curves fall short (PR03 nearest).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 09:30:17 +02:00
maximeandClaude Opus 5.5 294e024e5a Move Displacements into a tab of the Explore mockup and document the session (D-055)
The jumps and trends now sit in a Displacements tab after Diagnosis
(#tab=displacements), no longer in a separate sidebar page; a click on
a row opens the Diagnosis tab on that target.

Documented: what the client looks at (jumps and trends, not errors,
handled upstream) in docs/displacement/domaine/ce-que-regarde-le-client.md;
the expert's reading of NORDEND in the case journey; the experimental
way of working in vues-deplacements/CLAUDE.md; D-055, the spec, the
note, the README and the project map.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 18:26:58 +02:00