Files
aimsight-labeling/knowledge/barcelona-incident.md
T

24 lines
2.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# The Barcelona incident (19.09.2026)
The AIMsight documentation makes it its main regression case: roadmap, line 33 and §15; support context, §7-8 (example file, question "Why did D-300-A jump?"), §12.2, §16.1 and the example "Barcelona reference switching". Its data are in `data/CLARIDEN/` ("L9 BCN" export, from 17/09 22:00 to 20/09 21:50 UTC, 10-minute rate, 29 sensors including 5 references; 432 images at 10 min, one per measurement, zip times in UTC) and, coded, in case E-004 (`events/E-004/`).
## What is observed
According to the blind report of 2026-10-15 (`agent-diagnostic/rapports/2026-10-15T1346Z_CLARIDEN_19-09-matin/`), rechecked on the data:
- around 00:00 on 19/09, the references move relative to each other (`PR-291` and `PR-293` by +0.7 px in `relative_x`, `D-302-C` motionless); `sigma0` is multiplied by ten; `corr_x` of the targets drops without their raw position moving;
- at 06:10, the "-B" targets move alone in the image (0.8 to 1.4 px), the references motionless; `PR_BG` jumps by 17 px, its reflector is no longer visible, its `error_value` stays just under the threshold and its values (~11) are kept;
- from 06:40 to 07:30, the 29 sensors move together (+1.8 to +4 px in `y`), then partly come back; `corr_y` keeps a step until the end of the measurements: +0.5 to +1.2 on the "-A" targets, growing with the distance to the references, and −1.0 on `D-306-B`;
- no external cause on the images.
## Two readings
- **AIMsight documentation**: movement of the station and the camera, instability of the references (`PR_284`, `PR_291`), switches between compensation states, targets that remained measurable; *"primarily reference-network / compensation-state instability, not target tracking"*. The follow-up described is on the system side: pattern reset, reconfiguration, exclusion of `PR_284` considered, reference added.
- **Expert** (reported by the user on 2026-10-15): the structure moved, and the camera and the references with it; the system probably overestimates the amplitude; other measurement systems on the site saw a major anomaly, and the site was interrupted; the structure is a bridge, whose arch is sagging (user, 2026-10-24). This is the diagnosis of E-004: *monitored-object motion*, real movement, intervention.
The two do not exclude each other: an unstable compensation distorts the amplitude of a real movement. The measurements alone do not separate the structure from the camera when everything moves together; blind, the diagnostic agent concluded a *weak/unstable reference solution*, consequence undetermined.
## Consequences and questions
- For the correction of the curves (D-044): these jumps are, for the expert, a real movement; do not remove them as an artifact. The amplitude, however, is not established.
- Open: the documentation speaks of an SFTP export at 1 min and images at 15 min, here 10 min: is it the same set, reprocessed or not? `PR-284` is here only a local reference (`pattern_type` `ref`), outside the compensation.