- 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>
- 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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
Jumps: a sudden change within 2 h (8 times the target's usual 2-hour
change) that lasts 24 h (at least 1.4 times its daily swing); every
jump of the range, returns included, so PR17's return on 12/10 now
shows. Trends: Theil-Sen slope and Kendall tau of the daily levels,
jumps set aside, kept when the drift over the period reaches the daily
swing and goes steadily one way. Provisional thresholds; method and
results in vues-deplacements/contexte/detection-d-anomalies.md.
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>
- docs/displacement/domaine/incident-de-barcelone.md: the AIMsight
regression case is data/CLARIDEN/ (case C-004); what the data show,
the documentation's reading (reference/compensation instability)
against the expert's (real movement of the structure, confirmed by
other instruments, amplitude likely overestimated), open questions.
- nouveau-cas: platform zips date images in UTC, exports cover local
days; keep every image of the range, even at 10 min.
- colonnes-des-deplacements: native cadence is 15 or 10 min.
- CLAUDE.md: four cases in the base, displacement data of NORDEND,
WILDSTRUBEL and CLARIDEN.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Card checked section by section against the case data and images:
- header: "end of measurements" (images run to 23:00);
- summary, symptom: duration, most targets, uneven jumps;
- signature: corrected ratios and ranges, remaining references at 0,
jumps only at some switches (setting R2 aside alone moves nothing),
web visible by day too; C1 is a local reference, outside the
compensation;
- diagnosis: mechanism with one or two references set aside, inflated
MAD for several targets, "masked movement" line removed;
- proofs: three captions corrected; index line aligned.
Domain note: pattern_type `ref` is a local reference (station manual).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy the station's displacement export and images into the case folder,
with coded sensor names; the station takes the case number instead of
S01, and graphique.py / vignettes.py drop --alias (D-050).
Rewrite C-001 as the expert's diagnosis of this event only: summary,
symptom, verdict, signature with commands, diagnosis, evidence. Drop
exclusions, expected output, unknowns and test history; matching no
longer uses exclusions (D-051). The corr_x jumps at the reference
switches are judged negligible.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add the anonymiser-cas skill: a growing registry gives stable codes
(S01, R1, C1), a stdlib script rewrites a case and renames its files,
and graphique.py / vignettes.py take --alias to plot with codes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two analysis reports delivered to the client (GN-1.472, GN-5.054, May 2026)
go to docs/aimsight/ unchanged. Their diagnoses are summarized in
docs/displacement/domaine/cas-annotes-par-l-expert.md as reference truth
for displacement, without data: not in the diagnostic agent's case base.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>