- inventaire.py: what each source contains on the window (filled or empty columns, metric names, images), names and counts only
- analyser-lot: step 0 on the data, own scripts in <lot>/outils/, section 3 "Outils"
- tool-builder (the optimiser, rewritten): after the analyst, optimises or adds reading tools, never removes; no control yet
- /aiguiser skill, reader, corrector and voir.py removed; its sessions and spec stay as history
- docs: D-097, specs, CLAUDE.md, run.md, README, plan point 56; the shared files also carry another session's pending edits (D-096 entry, plan points 57 to 67)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- /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>
- 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>
- 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>
- 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>
- 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>
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>
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>
- 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>
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>
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>
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>
- 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>
- 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>
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>
Mechanical anomaly detection on the hourly displacements in mm, data
unchanged: for each target and axis, the largest gap between the median
of the next 24 h and the previous 24 h, kept above 3 times the target's
daily swing (provisional). Jumps within 6 h form one event, so a common
jump is not several anomalies. Grey curves for all targets, colour for
those that jumped; a click opens Explore, Diagnosis.
Note on the idea, first trial and leads in
vues-deplacements/contexte/detection-d-anomalies.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>