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 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>
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>
Ten screenshots of the monitoring site (Explore, Target Configuration,
System Summary, Measurements), SIM_CCID and IP addresses masked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Card checked against the case data and images:
- signature: corrected ranges (corr_y plateau up to +1.2, 18 to 126
MAD; error_value of the local group 3 to 7 times the previous day),
the local group moves far more than the other sensors, not alone;
- new criterion 4: at night the references move between themselves
(not R1), sigma0 rises tenfold and corr_x of most targets drops
without their raw position moving, a plateau that lasts to the end
of the measurements; images become criterion 5;
- event now starts on 18.09 at 23:20 (header, summary, symptom, index);
- diagnosis: night then morning in the mechanism; C24 sits in the
local group and its error_value rises from 05:50;
- figure 1 redone with a corr_x panel, captions corrected.
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>
Second run on the same question, case in the index: C-004, complete
match (criteria 1 to 4 verified); monitored-object motion with a
camera/reference compensation event, consistent with; consequence:
real movement; action: intervention. The card needed no change.
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>