- Every station's auto labels reviewed by an analyst (/review-auto-labels), then a
cross-review per family across all stations (new skill /cross-review-labels),
a finishing pass, and descriptions rewritten in words (no numeric values).
- The three never-labeled ranges (WILDSTRUBEL 07/09-01/10, NORDEND 16/08-01/10)
labeled and reviewed: 991 auto labels on 11 stations, labeling/controle.py at 0 errors.
- Labeling knowledge gathered in labeling/: regles-d-etiquetage.md (new), familles.md
(settled boundaries), connaissances/ (notes moved from docs/, links updated),
the label map rebuilt from reviewed labels, events and cases; events tied to their
stations (PS_DES_COUDRES is JUNGFRAU). The labeler and reviewers read only labeling/.
- labels-map reads auto labels and events; decision D-130; living plan points 73-75.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The analyst reviews labeling/auto/ labels on a range chosen by the user (bounds, one event, family, description, missed ones) and proposes corrected labels; the expert answers its questions, then the range is replaced. First run on BREITHORN October: 10 corrected, 25 and 26 merged, one missed night added; the expert confirms the camera's cold-night deviations are thermal (housing temperature, not air). Labels the expert settled carry "revue", read by /labels-map.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Work from another session, committed at the user's request. extraction/README.md also drops the /aiguiser mention (D-097).
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 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>
- 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>
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>
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>
- 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>